review-code — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited review-code (Agent Skill) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 1 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
ultrathink
Critique only — no fixes or implementation. Understand why the code exists before judging it.
Prefer in order: explicit <target>, changes made in this conversation, working diff. If unclear, ask.
Then gather enough context (PR/issue text, plans, surrounding code) to avoid misreads. Don't turn every review into archaeology — if a missing detail would materially change judgment, ask briefly.
Understand how important parts work before commenting line by line. Focus on load-bearing logic, edge cases, scope drift, and intentional tradeoffs.
For each finding: file path + line, why it matters, severity.
If something looks odd but context supports it, acknowledge rather than flag.
## Code Review: [scope]
**Verdict: {Approve | Request Changes | Reject}**
### Inferred Intent
[Only when context supports it]
### Critical Issues (Must Fix)
- `path/to/file:line` — concise description. Why: [reason]
### Suggestions (Nice to Have)
- `path/to/file:line` — concise description
### Questions
- [Clarifications on intent or tradeoffs]
### Summary
[1-2 sentences]Include only sections with content. Always include Verdict and Summary.
<target>$ARGUMENTS</target>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.