fai-review-and-refactor — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited fai-review-and-refactor (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
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.
Review code and apply targeted refactoring in a single disciplined pass.
| Dimension | What to Check |
|---|---|
| Correctness | Does it do what's intended? Edge cases handled? |
| Security | Injection, secrets, auth bypasses? |
| Performance | N+1 queries, missing indexes, unbounded loops? |
| Readability | Clear names, reasonable length, low complexity? |
| Testability | Can each function be tested in isolation? |
| Error handling | All external calls have try/catch? |
1. Review: Read through, note issues (don't fix yet)
2. Classify: Group issues by type (bug, readability, performance)
3. Prioritize: Fix bugs first, then readability, then style
4. Refactor: One fix per commit with tests passing
5. Comment: Leave review with both issues found and fixes applied| Review Finding | Refactoring |
|---|---|
| Long method (>50 lines) | Extract method |
| Deeply nested conditionals | Guard clauses (early return) |
| Duplicate code blocks | Extract shared function |
| Magic numbers | Named constants |
| God class | Split by responsibility |
| No error handling | Add try/catch with specific types |
**Issue:** [Category] — [Description]
**Severity:** 🔴 Bug | 🟡 Improvement | 🟢 Suggestion
**Suggestion:** [Concrete fix or code example]
**Why:** [Impact if not fixed]| Issue | Cause | Fix |
|---|---|---|
| Review too long | Trying to fix everything | Focus on top 3-5 issues per review |
| Refactoring introduces bugs | Changed behavior during refactor | Tests before AND after each change |
| Author defensive | Suggestions feel like criticism | Frame as questions: "Have you considered...?" |
| Review comments ignored | Too many minor nits | Separate blocking from non-blocking comments |
| Practice | Rationale |
|---|---|
| Tests before refactoring | Safety net for behavior preservation |
| One refactoring per commit | Easy to revert specific changes |
| No feature changes mixed in | Separate refactor from feature PRs |
| Measure complexity before/after | Prove improvement objectively |
| Small PRs (< 200 lines changed) | Easier to review thoroughly |
| CI must pass after each step | Catch breakage immediately |
fai-refactor-complexity — Reduce cyclomatic complexityfai-refactor-plan — Multi-sprint refactoring plansfai-code-smell-detector — Automated smell detectionfai-github-pr-review — PR review standards and merge policiesReview-and-refactor is complete when all blocking issues are fixed, tests pass before and after each change, and complexity metrics show measurable improvement.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.