dev-pipeline

Create an atomic commit for current changes

Execute an implementation plan file

Write a session handoff document for the next agent or session

Create a comprehensive implementation plan for a feature

Run the project's full validation suite with per-level reporting

Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.

Identifies code simplification opportunities for clarity and maintainability while preserving exact functionality. Use after writing or modifying code. Focuses on recently changed code unless told otherwise. Reports findings with before/after suggestions. Advisory only - does not modify files.

Use proactively to understand HOW code works. Analyzes implementation details, traces data flow, and documents technical workings with precise file:line references. The more specific your request, the better the analysis.

Comprehensive codebase exploration - finds WHERE code lives AND shows HOW it's implemented. Use when you need to locate files, understand directory structure, AND extract actual code patterns. Combines file finding with pattern extraction in one pass.

Analyzes PR test coverage for quality and completeness. Focuses on behavioral coverage, not line metrics. Identifies critical gaps, evaluates test quality, and rates recommendations by criticality (1-10). Use after PR creation or before marking ready.

The PRIMARY development workflow router for software engineering tasks. Routes development requests to specialized cookbooks based on intent. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for #42" IMPLEMENT — "implement the plan", "execute .claude/dev-pipeline/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR #123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming broken?", "root cause analysis on the timeout issue" COMMIT — "commit these changes", "commit the auth refactor" PR — "create a PR", "open a pull request for this branch" ISSUE — "report this to gh", "create a gh issue", "log it in github", "file a bug for this", "create a feature request" This skill triggers on ANY development task: researching, investigating, planning, building, reviewing, debugging, committing, or shipping code.

Replicate and validate a GitHub issue by spinning up the project's local app, analyzing the issue, and systematically testing all described symptoms using browser automation. Use when: User wants to reproduce a bug, validate a GitHub issue, confirm a reported problem, or investigate whether an issue is real before working on a fix. Triggers: "replicate issue", "reproduce issue", "validate issue", "confirm bug", "test issue", "can you reproduce", "try to replicate", "verify the bug". Capability: Detects the project's dev server config, switches to main, pulls latest, starts the app, reads the GitHub issue, then uses agent-browser to systematically test every symptom and produce a findings report. NOT for: Fixing issues (only reproduces and reports), general UI testing.

Autonomous rule adherence checker. Scans the codebase for rule violations, fixes the highest-impact ones in an isolated worktree, runs full validation, creates a PR. Uses memory to track progress across runs.

Save current task list for reuse across sessions

Triage GitHub issues by applying type, effort, priority, and area labels. Runs in an isolated context to avoid polluting the main conversation with issue details. Delegates to a specialized triage agent with label validation hooks.

6 hooks across 4 events