Piv Fix Review Findings
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.
Install
$ agentstack add skill-coleam00-skills-piv-fix-review-findings ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-coleam00-skills-piv-fix-review-findings) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 piv-validate skill to finalize the fixes.
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: coleam00
- Source: coleam00/skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.