piv-fix-review-findings
Skill0 starsChanged 57 days agoMITView on GitHub
Triage code-review findings (manual or AI), fix the ones you choose one at a time with tests, defer/log the rest, then validate — and if the work is on a PR, commit and push so the PR reflects the fixes. Use after a review has produced a list of issues or a review file.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- coleam00/skillsedited, first seen Nov 14, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- coleam00/skills★ 73897% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- feature-slicingSkill
- mermaid-diagramsSkill
- modern-cssSkill
- piv-commitSkill
- piv-create-prSkill
- plan-verify-fixSkill
- semver-releaseSkill
- slack-block-kitSkill
- slack-mrkdwnSkill
- verify-setupSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
If the Code-review is a file, read the entire file first so you understand every finding before triaging.
- Distinctive: line 30
Don't let the reviewer dictate scope — "real, but later" is a valid and common call.
- Distinctive: line 38
Create and run a test that proves it.
- Very specific: line 42
Run the project's full validation (tests, type-check, lint, build) to confirm nothing regressed, then run /code-review on the fixes so a …
- Very specific: line 47
If these fixes are on a PR branch, commit them (use piv-commit) and push so the PR reflects the fixes and the review can re-run on the …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Fix Review Findings
A review produced findings — but a review is input, not a work order. You decide what happens to each one.
Code-review (file or description of issues): $review
Direction / scope (what to fix now vs defer): $scope
If the Code-review is a file, read the entire file first so you understand every finding before triaging.
1. Triage first (the human's call)
Sort the findings before touching code. Honor any direction in the scope argument; if it's unclear, surface the findings grouped and ask rather than fixing everything by default:
- Fix now (this PR) — real, in-scope, belongs with this change.
- Defer / log as an issue — real but later; don't bloat this PR. Create a tracker issue (or note it) instead of fixing it here.
- Needs a human look / manual test — anything you should inspect or test by hand before trusting it. Flag it, don't silently auto-fix.
- Noise / won't-fix — say why, then drop it.
Don't let the reviewer dictate scope — "real, but later" is a valid and common call; a clean small PR beats a sprawling one.
2. Fix the "fix now" set — one at a time
For each:
- Explain what was wrong.
- Make the fix.
- Create and run a test that proves it.
3. Validate
Run the project's full validation (tests, type-check, lint, build) to confirm nothing regressed, then run
/code-review on the fixes so a fresh review confirms they didn't introduce new issues.
4. If operating on a PR — commit and push
If these fixes are on a PR branch, commit them (use piv-commit) and push so the PR reflects the fixes and the
review can re-run on the updated PR. If nothing was fixed (everything deferred), there's nothing to push — just make
sure the deferred items are logged as issues.
Output
A short report: what was fixed (with its test), what was deferred/logged (with issue refs), what needs a manual look/test — and, if on a PR, the pushed commit + confirmation the PR is updated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

