dacheng-gao/ai

superagents

Use when a matching specialist could materially improve accuracy or context isolation, or when a request spans independent work lanes.

develop-feature

Use when implementing a repository feature, integration, API or schema change, or other intentional behavior addition after the desired outcome is clear enough to build.

evolve-architecture

Use when evaluating or evolving an existing system's architecture, business or domain boundaries, cross-module flows, dependencies, reliability, scalability, security, or operability.

answer

Use when the user wants repository-grounded explanation, technical analysis, a command, or an approach comparison without asking for implementation or remediation.

fix-bug

Use when investigating and repairing a regression, crash, failing test, incorrect output, integration failure, or performance problem in a repository.

git

Use when inspecting or changing local Git state, including diffs, staging, commits, restores, reverts, and merge, rebase, or cherry-pick conflict resolution.

github

Use when reading or changing GitHub issues, pull requests, workflow runs, releases, repository metadata, or remote review context through the GitHub CLI.

refactor

Use when improving internal structure, dependencies, readability, maintainability, or performance without intentionally changing externally observable behavior.

review-code

Use when reviewing a pull request, staged diff, patch, commit, or repository files for defects, regressions, security risks, and missing verification without implementing fixes.

reviewing-product-requirements

Use when turning a feature idea, issue, stakeholder note, or incomplete specification into a concise, testable product requirement with explicit scope and open decisions.

writing-test-cases

Use when stable product requirements, a feature specification, or acceptance criteria need to become a prioritized test plan and traceable executable test cases.