All authors
Claude Skills by Jarryd-W-Hoffman
github.com/Jarryd-W-Hoffman7 skills0 installs10 views
- ReviewFour-pass code review. Runs four independent reviewer agents in parallel (completeness, correctness, compliance, consistency) against the same change, verifies borderline findings, and merges everything into one ranked report. Use when the user asks for a code review, PR review, pre-merge check, or "four-pass review" of the working tree, a branch, a PR number, or specific paths. Read-only; it never edits files or posts anywhere unless asked with --comment.Votes: 0GitHub stars: 3
- MapChange impact map. Finds the symbols a change touches and every reference to them with a script, then, unless --quick, runs one read-only impact-analyst agent to verify those references and find what grep cannot see — routes, scheduled tasks, queued jobs, event listeners, container bindings, tests that reach the change and changed code no test reaches, data and contracts. Writes impact.md and impact.json. Use when the user asks what a change affects, its blast radius, what depends on some cod...Votes: 0GitHub stars: 3
- CheckMigration safety check. Finds the database migrations in a change without a model and, only when there are some, runs one read-only migration-reviewer agent against them for what breaks in production — old code running against the new schema during the deploy, table locks and rewrites, data loss, constraints existing rows violate, edited history, and missing rollbacks — then writes one report and a findings.json in the shared finding contract. Use when the user asks whether a migration is saf...Votes: 0GitHub stars: 3
- HuntRegression hunt. Reads a change's history with a script, with no model — the commits that last touched the changed lines, the fixes and reverts among them, files that always change together with the changed ones — and, only when that history has something to say, runs one read-only regression-reviewer agent to check whether the change undoes it: removes a fix's guard, re-introduces reverted code, loosens a regression test, or leaves a usual partner file behind. Writes one report and a finding...Votes: 0GitHub stars: 3
- AllFull review of a change. Works out from the files it touches, with no model, which of this marketplace's plugins it needs (fourpass, migrations, regressions, impact), runs the selected ones in parallel, each exactly as it runs on its own, and merges their results into one report with one verdict. Offers testgaps afterwards, never without asking. Use when the user asks for a full, complete or engineering review of a change, PR or branch. To see only which plugins would run, use /review:plan.Votes: 0GitHub stars: 3
- PlanReview plan for a change. Works out from the files a change touches, with no model, which of this marketplace's plugins it needs (fourpass, migrations, regressions, impact) and which follow-ups to offer (testgaps), and shows the plan with the files that selected each plugin and the reason each other plugin is skipped. Runs nothing and costs nothing. Use when the user asks which reviews a change needs or what /review:all would run.Votes: 0GitHub stars: 3
- WriteWrite tests that prove review findings. Takes the findings from a four-pass review (the report, a findings.json, or one request in plain words), launches one test-writer agent per finding in parallel, and merges the results into one report that says, per test, whether it reproduced the defect, covered the gap, or could not be written. Use when the user asks to write tests for a review's findings, to reproduce a finding as a failing test, or to cover a change the review called untested. Edits ...Votes: 0GitHub stars: 3