Use this agent to review authentication and authorization code for security issues, design flaws, and best practice violations. Trigger when the user mentions "review auth", "is my login secure", "check authentication", "review authorization", "auth security", "password security", "JWT review", "session security"…
Use this agent to map, analyze, and optimize Next.js route structure. Trigger when the user asks to "map routes", "analyze routing", "find missing error boundaries", "check loading states", "review middleware", "list all pages", "find route issues", or needs a comprehensive view of their Next.js application structure.…
Independent falsify pass for review-gate findings. Receives unified diffs + a findings list and returns the IDs of findings to drop. Spawned by the /review-gate:review orchestrator after the code-reviewer. Not for general questions.
Reviews all changed files in a change set in an isolated context and returns structured findings as JSON. Spawned by the /review-gate:review orchestrator. Not for general questions.
Git commit specialist with deep knowledge of version control best practices and semantic commit messages. Automatically runs language-specific quality checks (formatters and type checkers) before committing code changes. Use when ready to commit changes to git.
Documentation architect specializing in creating precise, consolidated technical documentation. Analyzes existing documentation patterns, eliminates duplication, and maintains consistency across large codebases. Use proactively when features are completed or documentation needs review.
Reviews code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter.
Lightweight agent for Fizzy.do task management without cluttering your main conversation context. Use for listing boards, creating cards, syncing todos, or closing completed work.
Generate the instruction bundle (AGENTS.md body, SOUL.md, HEARTBEAT.md, TOOLS.md) for a single Paperclip company agent. Use during company generation to write all agent files in parallel — one agent-creator instance per paperclip agent. Context: Company generation Phase 6a — writing agent files in parallel user…
Create properly structured SKILL.md files for Paperclip company agents. Use during company generation to write all custom skills in parallel. Context: Company generation Phase 6 — writing custom skills user: "Write 12 custom SKILL.md files for Figurio" assistant: "I'll use the skill-creator agent to generate properly…
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
Reviews OpenAPI specification files against REST API and IAM permission-naming guidelines. Runs a deterministic Spectral lint against the bundled ruleset first (silently skipped when no Spectral CLI is available), then reviews what a linter cannot express. Checks version consistency, required elements, naming…
Synthesises Jira data, per-repo diff summaries, and confirmed write targets into a documentation checklist the writer follows and the reviewer checks against. Detects the repo's image policy (local vs CDN-upload) and annotates per-screenshot placement. Does NOT write content. Model tier assigned by the caller per the…
Reviews product documentation written by /document for correctness, completeness, and fitness for purpose. Returns PASS / PASS WITH RECOMMENDATIONS / BLOCK. Uses Claude Opus. Epic drafts are reviewed by epic-reviewer (a separate agent); this reviewer is product-docs-only.