Loading...
Loading...
Found 80 Skills
Stage 1 spec compliance review. Triggers: /review stage 1. Verifies implementation matches design specification — functional completeness, TDD compliance, and test coverage. Do NOT use for code quality checks — use quality-review instead. Do NOT use for debugging.
Request coding agents to review code, verify review results and fix confirmed issues
Attack a code change and report what survives. Dispatches independent reviewers in parallel, each with a single job and no access to the implementer's reasoning: one hunts correctness bugs blind to the issue, one hunts requirement gaps against the issue text, one runs outside the process entirely. Optionally re-attacks its own findings, then synthesizes what is left. Returns findings and changes nothing — no tooling, no autofix, no edits. On request it publishes to the author, gated on demonstrated evidence. Every phase is configurable.
Handle a pull request from whichever side you are on. On someone else's branch it attacks the diff through changes-review, then publishes a real review with per-line comments and a verdict. On your own it works the threads people and bots left — decides its standing in each, verifies the claim before answering, runs the project's checks, then replies and resolves. Changes no code unless asked.
Write Rust tests to verify correctness of Rust code.
Implement a GitHub issue end-to-end using TDD, following the Agent Brief contract. Use when user wants the agent to pick up a ticket, write code to fulfill its acceptance criteria, commit, push, and close the issue.
Implement an agreed task incrementally and verify the result.
Use when you have a written implementation plan to execute with review checkpoints
Creates or updates TODO_LIST.md by reading all .md files in the project using sub-agents, then verifies which TODOs are already done by checking the actual code. Use when the user wants to build a comprehensive TODO list from existing documentation, verify TODO status against code, or says "build TODO list".
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Team-orchestrated implement → verify → fix → archive cycle
Collaborative coding with enforced micro-steps: announce, show diff, wait for confirmation, apply, verify. User controls pace with commands. Works with any domain agent as the executor. Use when: "pair program", "pair with me", "let's code together", "step by step coding", "walk me through implementing", "code with me"