agtop

Reviews implemented features against a specification file to verify the implementation matches requirements. Compares git diffs with spec criteria, optionally captures screenshots of critical UI paths, and produces a structured JSON report with issue severity classification. Use when a user wants to review work against a spec, validate an implementation, check if features match requirements, or verify work before merging. Triggers on "review the spec", "review my work", "validate against the spec", "check the implementation", "review this feature", "does this match the spec", "spec review", "review before merge". Do NOT use for implementing features (use the implement skill). Do NOT use for creating or writing specs (use the spec skill). Do NOT use for running tests or linting directly — the build skill handles validation.

Analyzes a feature spec and decomposes it into smaller, focused sub-tasks when the feature is too large for a single agent. Produces a task graph with mini-specs for each sub-task. Use when a user wants to break down a large feature, decompose a spec, split a plan into subtasks, or when a spec is too big to implement in one pass. Triggers on "decompose this spec", "break this down", "split into subtasks", "this is too big". Do NOT use for implementing features (use the implement skill). Do NOT use for creating specs (use the spec skill).

Implements a development plan by reading it, breaking it into tasks, writing the code, and reporting a summary of completed work. Use when a user wants to implement, execute, build, or code a plan. Triggers on "implement this plan", "execute this spec", "build this feature from the plan", "code this up", "follow this plan", "implement the spec", or when given a spec file path or inline plan text. Do NOT use for creating or writing specs (use the spec skill instead). Do NOT use for reviewing, critiquing, or modifying existing plans without implementing them. Do NOT use for running or deploying applications.

Creates structured implementation specs for development tasks categorized by conventional commit types (feat, fix, refactor, perf, chore, docs, test, build, ci). Use when a user wants to spec, plan, design, or scope work before implementing it. Triggers on "spec a feature", "create a spec", "scope this work", "design the approach", "write a spec for", "spec this fix", "spec a refactor", or when given a task description. Do NOT use for implementing or executing existing specs. Do NOT use for quick single-line changes that need no spec phase.

Implements a development plan by reading it, breaking it into tasks, writing the code, and reporting a summary of completed work. Use when a user wants to implement, execute, build, or code a plan. Triggers on "implement this plan", "execute this spec", "build this feature from the plan", "code this up", "follow this plan", "implement the spec", or when given a spec file path or inline plan text. Do NOT use for creating or writing specs (use the spec skill instead). Do NOT use for reviewing, critiquing, or modifying existing plans without implementing them. Do NOT use for running or deploying applications.

Reviews all uncommitted changes, groups them by logical concern, and creates atomic git commits — one per distinct change — using conventional commit message format. Use when a user wants to "commit", "commit my changes", "create commits", "commit this work", "stage and commit", "save my progress", "generate commits", "make atomic commits", or "commit everything". Also triggers on "git commit" or "check in my changes". Do NOT use for pushing to remote (use git push directly). Do NOT use for creating pull requests (use the pr skill). Do NOT use for reverting or amending commits.

Creates a GitHub pull request from the current branch by analyzing commits, generating a conventional title and structured body, pushing to origin, and submitting via gh pr create. Use when a user wants to "create a pr", "open a pull request", "submit a pr", "push and create pr", "make a pr", "pr this", or "ship it". Also triggers on "create pull request" or "open pr". Do NOT use for committing changes (use the commit skill). Do NOT use for pushing without a PR (use git push directly). Do NOT use for reviewing existing PRs.

Analyzes the user's prompt and project context to select the most appropriate workflow. Returns a workflow name that the executor uses to override the current skill sequence. Use as the first skill in workflows that need intelligent routing based on task complexity.

Discovers and executes the project's validation suite — linting, type checking, unit tests, and integration/e2e tests — fixing any failures found, then returning results in a standardized JSON format for automated processing. Auto-detects available test commands from the project's task runner or package manager. Use when a user wants to run tests, validate the application, check code quality, or verify the app is healthy. Triggers on "run tests", "test the app", "validate the application", "run the test suite", "check for errors", "run all checks", "is the app healthy". Do NOT use for implementing features (use the implement skill). Do NOT use for reviewing against a spec (use the review skill). Do NOT use for starting the dev server (use the start skill).

Generates concise markdown documentation for implemented features by analyzing git diffs against the base branch and optionally referencing the original specification. Creates docs in docs/ with technical details, usage instructions, and optional screenshots. Use when a user wants to document a feature, generate feature docs, write up what was built, create implementation documentation, or summarize changes for a completed feature. Triggers on "document this feature", "generate docs for this feature", "write up what was built", "create feature documentation", "write docs for this branch". Do NOT use for implementing features (use the implement skill). Do NOT use for reviewing features against specs (use the review skill). Do NOT use for creating plans or specs (use the spec skill). Do NOT use for general README or project documentation.

A test skill for unit testing

Reviews all uncommitted changes, groups them by logical concern, and creates atomic git commits — one per distinct change — using conventional commit message format. Use when a user wants to "commit", "commit my changes", "create commits", "commit this work", "stage and commit", "save my progress", "generate commits", "make atomic commits", or "commit everything". Also triggers on "git commit" or "check in my changes". Do NOT use for pushing to remote (use git push directly). Do NOT use for creating pull requests (use the pr skill). Do NOT use for reverting or amending commits.

Creates a GitHub pull request from the current branch by analyzing commits, generating a conventional title and structured body, pushing to origin, and submitting via gh pr create. Use when a user wants to "create a pr", "open a pull request", "submit a pr", "push and create pr", "make a pr", "pr this", or "ship it". Also triggers on "create pull request" or "open pr". Do NOT use for committing changes (use the commit skill). Do NOT use for pushing without a PR (use git push directly). Do NOT use for reviewing existing PRs.

Builds deep codebase context by systematically scanning the project structure, reading key documentation, and summarizing understanding. Use when starting a new session, onboarding to the codebase, or when asked to "prime", "get context", "learn the codebase", "orient yourself", "understand the project", or "familiarize yourself with the code". Also triggers when asked "what does this project do" or "summarize the codebase". Do NOT use for implementing features, fixing bugs, or running commands. Do NOT use when already primed in the current session.

Start your application by discovering and running the development server and any required background services. Auto-detects the start command from the project's task runner or package manager. Use when a user wants to start, run, launch, or boot the application. Triggers on "start the app", "run the dev server", "launch the application", "boot it up", "start the server", "spin up the app". Do NOT use for running tests, linting, or type checking (use the test skill or run commands directly). Do NOT use for deploying to production or staging environments.

Creates, converts, or improves Claude skills. Converts existing .claude/commands/ slash commands into skills, builds new skills from a prompt, or refactors existing skills to follow best practices. Use when a user wants to "convert a command to a skill", "turn this slash command into a skill", "create a skill", "build a skill", "make a new skill for X", "scaffold a skill", "generate a skill", "improve this skill", "refactor this skill", or "update this skill". Also triggers for "upgrade this command", "make a skill that does X", or when given a path to an existing skill with an improvement request. Do NOT use for implementing features, fixing bugs, running existing skills, or general code generation that is not a Claude skill.