Skill323 repo starsupdated today

post-merge-scan

The post-merge-scan skill automatically audits code merged in the last seven days to identify technical debt and integration issues such as TODO comments, deprecated API usage, broken documentation links, and stale feature flags. It categorizes findings by risk level and effort, then recommends appropriate follow-up actions ranging from minimal fixes to human escalation, designed for off-peak execution in continuous integration workflows.

View source Repository: loop-engineering

Install in Claude Code

Copy

git clone --depth 1 https://github.com/cobusgreyling/loop-engineering /tmp/post-merge-scan && cp -r /tmp/post-merge-scan/starters/post-merge-cleanup/.grok/skills/post-merge-scan ~/.claude/skills/post-merge-scan

Then start a new Claude Code session; the skill loads automatically.

Definition

SKILL.md

# 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.