Review local changes, branches, commits, and PRs with independent native subagents. Use for code-review requests or substantive implementation closeout; focus on concrete defects, simplicity, and the task's goal.
Present concise plans, progress updates, findings, and final reports that keep the human oriented, informed, and able to learn how the project works. Use for complex agent coding work and focus on the most important points and decisions.
Create a self-contained HTML explanation when the user requests one or when important, durable project knowledge is materially easier to understand visually than in concise chat. Use for significant architecture, research, decisions, incidents, audits, or changes that the user may revisit. Do not use for routine…
Find important, high-confidence correctness bugs and edge cases in an existing codebase. Use when the user asks to inspect a repository, subsystem, or implementation for bugs, failure modes, incorrect behavior, or overlooked edge cases.
Find why an agent produced a bad result, strengthen the code, repository, verification, tooling, or workflow that enabled it, then retry the original task. Use when the user asks to learn from a mistake, prevent recurrence, or postmortem an agent failure.
Clarify a new task by stating the goal the agent believes the user wants, showing its current understanding, and asking only product-related or high-priority questions that could materially change the outcome. Use before planning or implementation when the task needs alignment.
Audit agent skills for triggering quality, correctness, context efficiency, redundancy, structure, failure guidance, and coverage gaps. Use when the user asks to review, improve, compare, simplify, or evaluate skills in global, repo-local, Claude, Codex, or custom skill paths.
Set up or refactor a repository so agents naturally follow its intended architecture and important mistakes fail mechanically. Use when the user invokes $repo-setup, asks to make a repo agent-friendly, or wants important repository rules enforced through structure, types, tooling, tests, or CI.
Record a small MP4 while demonstrating or verifying a UI change, then attach the video as proof. Linux cloud sessions record the private virtual display; macOS records only the app window under test. Use for any repo whenever a UI change is verified or demoed.
Run a session as a project coordinator and product partner: keep a board, dispatch work to subagents and task-card threads with a standard brief and workflow, track them with a check loop, and report to the human in priority order. Use when the user asks you to coordinate a project, act like Claude Projects, spin up…
★not rated 47 8d agoA81 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: