KG

Use when starting any conversation - establishes how to find and use codebase-pilot skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Analyzes the blast radius of a file change — finds all dependents, transitive imports, affected tests, and risk score. Best before modifying shared files like types, utilities, or core modules.

Packs and compresses the codebase into an AI-friendly context file. Best for new features, code reviews, or full codebase context with minimal tokens.

Full project health check — chains pack analysis, secret scan, token budget, and impact overview in a single pass. Saves tokens by combining all checks into one context load.

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Scans the codebase for leaked secrets, API keys, passwords, and credentials. Best before committing code or reviewing security posture. 180 patterns across 15 categories.

Use when executing implementation plans with independent tasks — dispatches fresh subagents scoped to agents.json boundaries

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when implementing any feature or bugfix, before writing implementation code

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Checks token counts per file and plans context budget. Shows which files consume the most tokens and how to optimize context window usage.

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment