Loading...
Loading...
Found 127 Skills
Adopt the Three Provinces and Six Ministries style code review, output structured review conclusions in five stages: Zhongshu Sheng, Shangshu Sheng, Six Ministries, Menxia Sheng, and Jinyiwei
Hunts complexity in the current diff and APPLIES the simplifications directly to the working tree, then verifies the build. Five angles: reuse (duplicate logic, hand-rolled stdlib, platform features), quality (React/TypeScript hygiene, over-memoisation, exhaustive-deps, `any`, `CLAUDE.md`/`AGENTS.md` violations), efficiency (unnecessary work, missed concurrency, hot-path bloat), altitude (bandaid fixes special-cased onto shared code), and test discipline (repro test per bug fix, useless tests deleted, new tests only when they prevent a named failure). Hand it a `pr-reviewer` report and it applies those confirmed findings too. Use when the user says "tidy this up", "simplify", "clean up this diff", "polish my changes", "make this simpler", "apply the review findings", or "any reuse opportunities?". For a read-only report instead, use `pr-reviewer`; for the PR's title, description, or commits, use `pr-creator`.
Teach the user something from the code in front of them. First ask what to learn - how the codebase works, what the recent changes (including ones AI just made) do, or a topic the user names - then read the code and teach techniques used, better approaches missed, and concepts worth studying. Use when the user says "/debrief", or asks what they can learn from their recent work, branch, changes, or this codebase.
Diff-aware AI browser testing — analyzes git changes, generates targeted test plans, and executes them via agent-browser. Reads git diff to determine what changed, maps changes to affected pages via route map, generates a test plan scoped to the diff, and runs it with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, running regression checks on changed components, or validating that recent code changes don't break the user-facing experience.
Review PRs: diffs, inline comments via gh or REST.
Write a Guided Review (a chaptered walkthrough of a changeset with the real diffs inline) and turn it into one portable HTML file with `plannotator guide export`. Use when someone asks for a guide, walkthrough, tour, or explainer of a diff, branch, PR, or commit, or wants a shareable review guide. Needs git and the plannotator CLI.
Turn a PR, branch, commit, or git diff into an interactive visual recap with diagrams, file maps, API/schema summaries, annotated diffs, and focused review notes.
Reviews code changes and provides actionable feedback. Use when the user asks to review a PR, diff, commit, or code changes. Triggers on "/review", "review this PR", "review my changes", "code review".
Generate appropriate commit messages based on Git diffs
Parallel read-only multi-agent review of a current git diff or explicit file scope to find behavioral regressions, security or privacy risks, performance or reliability issues, and contract or test coverage gaps. Use when the user asks for a review swarm, parallel review, diff review, regression review, security review, or wants high-signal issues plus a prioritized fix path without editing files.
Generates conventional commit messages by analyzing git diffs and changes. Use when writing commit messages, following commit conventions, or documenting changes.
This skill should be used when the user asks to "review my changes", "review this code", "check my work", "what's wrong with my changes", "review before I push", "security review", "do a code review", or mentions reviewing, auditing, or analyzing local code changes before committing or opening a PR.