Skill reference
Every skill, every argument
Run a skill as /hp-review-toolkit:<skill> with the plugin, or /<skill> with the skills CLI. Whatever you type after the name is its argument. In agents without slash commands, ask for the skill by name.
review-pr
read-onlyThe full review. It writes review-report/findings.json, the source of truth, and report.html: a verdict, the severity mix, a risk heatmap by area, the safety fact the change rests on and how well it's proven, the mistake classes it found, a conventions scorecard, a test-gap matrix, and a deploy checklist. On your own branch it first runs the checks your CI runs, picked from the workflow itself, and notes any changed file none of them cover. It ends with a short summary in chat.
- No argument
- The current branch against main.
482- That pull request, fetched with gh.
github.com/…/pull/482- A pull request URL.
feature/wbs-tree- A branch against its base.
shard-threshold=250- Shard earlier than the default 400 changed lines.
budget=20- Keep more findings above the fold.
holistic- Also run the whole-diff generalist and compare.
interrogate=3- Also run three adversaries that break the change by running it. Your own checkouts, or under ## Trust.
context=docs/review.md- Use another context file.
repo=../other-checkout- Review a pull request in a different checkout than the one you're in.
no-report- Findings only: the full pipeline and findings.json, no HTML and no fixing. Fix later with resolve-review.
resolve-review
writes codeThe fixer, run on its own after a review. It plans the fixes by severity, makes one scoped edit per finding on your own branch (every site of a grouped finding), checks each one with the checks your CI runs, and reverts any fix that breaks them. A finding marked as a class gets hardened with fix-the-class after its sites are fixed, and any sibling outside the branch's scope is named by file and line. After the fixes it re-runs the review's safety-fact probe, and with a verify skill it drives the features the review touched. Deploy steps and PR-text issues come back as a list for you.
- No argument
- Verified findings at medium severity and up.
high- Only high severity and up.
conventions- Only one lens, feature area, or set of finding ids.
review-fix
writes codeThe fast local loop, and the one to point agents at. It runs the full review in findings-only mode, then fixes what it can on the current branch and reports a resolution table in chat, with a list of what only you can close. It never commits.
- No argument
- The current branch against main, fixed in place.
feature/x- Review and fix that branch.
publish-review
posts to GitHubPosts a finished pull-request review as one real GitHub review. Findings anchored in the diff become inline comments, and the rest folds into the review body, which opens with the safety fact and the mistake classes. It always shows you a dry run first and posts nothing until you confirm.
- No argument
- Inline comments for every finding that can anchor.
gist- Also host the report as a secret gist and link it. Public repos only.
pages owner/name- Host the report through a repo that publishes GitHub Pages instead, the private-repo route.
recap- Add the system recap: to the description of your own PR, or to the review body on anyone else's.
medium- Inline comments for medium and up only.
body-only- One summary comment, no inline comments.
https://…/report.html- Link a report you host yourself as the full report.
review-issues
posts to GitHubFiles the review's non-blocking findings, such as readability, naming, and soft conventions, as GitHub issues so they get fixed later instead of dying with the report. One issue per defect class, never per nitpick, deduplicated across runs and labeled review-debt for a scheduled fixer to drain. It asks before creating anything.
- No argument
- File low and nitpick findings from the latest review.
medium- Widen the band to medium and below.
category=Readability- Only one category.
path=review-report/findings-pr41.json- File from an archived findings file instead of the latest review.
yes- Skip the confirmation, for routines that already carry consent.
map-primitives
writes docsMaps your system's primitives into docs/primitives.md and primitives.yaml across data, API, auth, workflows, agent tools, UI, and infrastructure, and reports drift: the same concept declared in several shapes. It writes down loose ends honestly instead of quietly fixing them, so consolidation lands as its own PRs.
- No argument
- Bootstrap a map when there is none, or refresh it against the code and report new drift.
create-verify-skill
writes a skillGenerates a repo-local verify-<app> skill and its feature map, or refreshes them. It interviews the repo (how it runs, its seed data and test users, its test harness), writes the skill, maps your main features with the source files behind each, and drives one feature end to end before it hands over. Refresh checks every feature against the code and one live run, and leaves only proven corrections. It never touches product code.
- No argument
- Bootstrap, or refresh when a verify skill already exists.
refresh- Refresh only. Stops if there is no verify skill yet.
fix-the-class
changes the repoFor a mistake the repo has seen before. It finds the mistake classes in the repo's own record (reverts, review findings, review-debt issues, notes in AGENTS.md, workaround comments) and makes each one impossible at the highest level that works: architecture, types, a check whose error names the fix, a test, and prose only as a last resort. Every new check has to fail on a real past instance before it counts. It keeps a table in AGENTS.md of each rule and what enforces it. It runs only when you invoke it by name; resolve-review follows the same steps for a review's class findings.
- No argument
- Harden the class behind the correction you just gave, or, with no fresh correction, every class the record shows.