Scan recent merges to main for follow-up cleanup: TODOs, deprecations, broken doc links, stale flags. Use in post-merge cleanup loops.
Scanned 6/13/2026
Install via CLI
openskills install cobusgreyling/loop-engineering---
name: post-merge-scan
description: >
Scan recent merges to main for follow-up cleanup: TODOs, deprecations,
broken doc links, stale flags. Use in post-merge cleanup loops.
user_invocable: true
---
# Post-Merge Scan Skill
## Output per merge
```markdown
### 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.No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...