post-merge-scan

Scan recent merges to main for follow-up cleanup: TODOs, deprecations, broken doc links, stale flags. Use in post-merge cleanup loops.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./starters/post-merge-cleanup/.claude/skills/post-merge-scan/SKILL.md

Post-Merge Scan Skill

Output per merge

### PR #N — title (merged DATE)
- Follow-ups found: (list with file:line)
- Risk: low | medium | high
- Effort: small | medium | large
- Suggested loop action: minimal-fix | ticket | escalate-human | skip

What to look for

TODO / FIXME introduced in merge
Deprecated APIs still referenced
Broken internal doc links
Stale feature flags marked for removal
Unused imports or dead code clusters (small only)

Rules

Only scan merges from the last 7 days unless state says otherwise.
Large refactors → ticket, not auto-fix.
Medium+ risk paths → escalate-human.
Be concise — this runs off-peak, not during active dev hours.

Repository: cobusgreyling/loop-engineering
Path: starters/post-merge-cleanup/.claude/skills/post-merge-scan/SKILL.md
Commit: 804a4e9

Last updated: about 12 hours ago
First committed: 2 months ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.