fno

Cancel an active target pipeline

TDD-disciplined task executor. The worker agent that implements individual tasks with test-first methodology. Returns structured SUCCESS/FAILED/BLOCKED results.

Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code follows the established patterns in CLAUDE.md. Also the agent needs to know which files to focus on for the review. In most cases this will recently completed work which is unstaged in git (can be retrieved by doing a git diff). However there can be cases where this is different, make sure to specify this as the agent input when calling the agent. Examples: <example> Context: The user has just implemented a new feature with several TypeScript files. user: "I've added the new authentication feature. Can you check if everything looks good?" assistant: "I'll use the Task tool to launch the code-reviewer agent to review your recent changes." <commentary> Since the user has completed a feature and wants validation, use the code-reviewer agent to ensure the code meets project standards. </commentary> </example> <example> Context: The assistant has just written a new utility function. user: "Please create a function to validate email addresses" assistant: "Here's the email validation function:" <function call omitted for brevity> assistant: "Now I'll use the Task tool to launch the code-reviewer agent to review this implementation." <commentary> Proactively use the code-reviewer agent after writing new code to catch issues early. </commentary> </example> <example> Context: The user is about to create a PR. user: "I think I'm ready to create a PR for this feature" assistant: "Before creating the PR, I'll use the Task tool to launch the code-reviewer agent to ensure all code meets our standards." <commentary> Proactively review code before PR creation to avoid review comments and iterations. </commentary> </example>

Resolve git rebase conflicts during auto-merge. Bias: preserve both sides where compatible. Refuse on migration/secret/lockfile files. One-shot; must stage resolved files and emit JSON summary.

Full /impeccable pipeline executor. Synthesizes the shape brief from the /think design doc + per-task AC list, selects /impeccable stages per task content, runs production-readiness passes (craft/polish/critique/harden/audit/layout), classifies findings, and returns a two-tier verdict with deferred_findings for operator to parse.

Analyzes integration and journey test coverage for code changes. Use this agent when: reviewing code changes for test coverage gaps, checking if journey tests exist for features, verifying database assertions in tests. <example> Context: User is running /review on changes to attendance feature user: "Review my changes" assistant: "I'll launch the integration-test-analyzer to check test coverage for your changes." <commentary> The sigma-review skill orchestrates this agent to analyze test coverage specifically. </commentary> </example>

Dispatch and message background agent workers from a runner-less surface (phone / Happy app). One router over the shipped `fno agents` mesh: spawn (launch a build worker), handoff (continue a doc without re-deriving a plan), discuss (open a daemon-managed chat thread), send (message a peer over the bus), watch/list/logs (observe), stop (terminate). Normalizes messy input (smart quotes, name, provider, mode), confirms billed launches, and reports the real receipt - never a fabricated one. Works for claude, codex, and gemini (handoff/discuss are claude-only in v1). Use when: 'spawn a worker for ab-XXXX', 'hand off this doc to a worker', 'open a discussion thread', 'send a peer a message', 'run /target in the background', 'ask codex <question>', 'list/watch/stop my agents'.

Multi-perspective feature completeness analysis and planning loop. Use when: 'audit feature', 'what's missing', 'feature completeness', 'gap analysis', 'discover features to build', 'plan all features'.

Self-improvement loop for the toolkit. Captures corrections passively (git post-commit, pre-commit verifiers, /insights tags) into ~/.fno/corrections.log, then runs a monthly review via a fresh Claude API call against the current rule text and surfaces patches the user triages in 20 minutes. Use when the user asks to review corrections, run an autocorrect review, triage proposed patches, install the autocorrect schedule, ingest /insights, check autocorrect status, or audit recurring mistake classes in the toolkit.

Create implementation blueprints (plans). Default: multi-phase BDD folder plan with waves and parallel execution. Use 'quick' for flat single-file plans for bugs and 1-session work. Use when: 'create plan', 'implementation blueprint', 'break this down', 'how should we build'.

Keep prompt cache alive during idle. Prevents 10x cost spike when cache expires. Use when: 'keep cache warm', 'cache keepalive', or auto-activated at session start when project opts in.

25 hooks across 15 events