post-merge
Skill1 starsChanged 7 months agoMITView on GitHub
Sweep for follow-up work after recent merges — TODOs added in merged PRs, stale feature flags, dead code, documentation gaps, and tech-debt tickets left by merge comments.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- jerseycheese/agent-skillstheir own version, first seen Oct 28, 2026
- ihyonoo/skillstheir own version, first seen Oct 20, 2026
- shinobiashi/claude-skillstheir own version, first seen Oct 8, 2026
- Docat0209/SoloForgetheir own version, first seen Apr 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- jerseycheese/agent-skills★ 4same name
- Docat0209/SoloForge★ 1same name
- ihyonoo/skills★ 0same name
- shinobiashi/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository206 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-healthSkill
- skill-validatorSkill
- accessibilitySkill
- agent-debugSkill
- agent-evaluateSkill
- ai-governanceSkill
- ai-system-reviewSkill
- api-docs-generateSkill
- api-examplesSkill
- api-mockSkill
- api-test-generateSkill
- api-validateSkill
- architecture-diagramSkill
- ask-mattSkill
- assumption-mapSkill
- boilerplateSkill
- brainstormSkill
- branch-finishSkill
- briefingSkill
- browser-testing-with-devtoolsSkill
- bundle-analyzeSkill
- cache-strategySkill
- canarySkill
- carefulSkill
- cavemanSkill
- changelog-autoSkill
- chaos-testSkill
- ci-setupSkill
- ci-sweepSkill
- cleanprojectSkill
- click-path-auditSkill
- codebase-designSkill
- code-review-checklistSkill
- code-tourSkill
- commitSkill
- completion-verifySkill
- complexity-reduceSkill
- component-librarySkill
- config-cleanupSkill
- config-generateSkill
- conflict-resolveSkill
- container-optimizeSkill
- context-budgetSkill
- context-engineeringSkill
- context-restoreSkill
- context-saveSkill
- continuous-learningSkill
- contributingSkill
- cost-trackSkill
- councilSkill
- create-todosSkill
- cross-modal-reviewSkill
- database-connectSkill
- db-diagramSkill
- ddd-modelSkill
- debug-root-causeSkill
- debug-sessionSkill
- debug-systematicSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 142
Non-GitHub repo: Use git log --merges only.
- Distinctive: line 152
Early exit: No merges in the target window → single-line report and exit.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Post-Merge Cleanup
Catch the follow-up work that gets left behind when a PR merges. Scans recent merges for TODOs, deprecated paths, stale flags, and doc gaps — then surfaces a prioritized cleanup list.
Usage
/post-merge # sweep merges from the last 24h
/post-merge --since <date> # merges since a specific date
/post-merge --pr <number> # sweep a specific merged PR
/post-merge --report-only # surface items without opening issuesBehavior
Step 1 — Find recent merges
# Get merged PRs in the target window
gh pr list --state merged --limit 20 \
--json number,title,mergedAt,files,body,headRefName \
--jq 'sort_by(.mergedAt) | reverse | .[:10]'Or use git log for repos without GitHub:
git log --merges --since="24 hours ago" --oneline
git log --merges --since="24 hours ago" --format="%H %s" | head -10Step 2 — Scan for TODOs and follow-ups
# TODOs added (not removed) in recent merges
git log --merges --since="24 hours ago" --format="%H" | while read sha; do
git diff "${sha}^" "$sha" | grep "^+.*TODO\|^+.*FIXME\|^+.*HACK\|^+.*XXX" | grep -v "^+++"
done | head -30
# Merge commit messages mentioning follow-up
git log --merges --since="24 hours ago" --format="%s %b" | \
grep -i "follow.up\|tech.debt\|cleanup\|todo\|later\|next.pr\|separate.ticket" | head -10Step 3 — Detect stale feature flags
# Find flags that were activated in the merge and may need cleanup
git log --merges --since="24 hours ago" --format="%H" | while read sha; do
git diff "${sha}^" "$sha" | grep -E "^\+.*(feature_flag|featureFlag|FEATURE_|isEnabled|FLAG_)" | grep -v "^+++"
done | head -20
# Find flags that may have been permanently enabled (defaulted to true)
grep -rn "feature_flag\|featureFlag\|FEATURE_" --include="*.ts" --include="*.py" --include="*.js" . | \
grep -i "= true\|= True\|: true" | head -10Step 4 — Check for dead code introduced
# Functions or classes added in the merge that are never called
git log --merges --since="24 hours ago" --format="%H" | while read sha; do
git diff "${sha}^" "$sha" --name-only
done | sort -u | while read file; do
# Check for exported symbols with no import elsewhere
grep -n "^export function\|^export class\|^def \|^class " "$file" 2>/dev/null | head -5
doneStep 5 — Identify documentation gaps
# New public API surface added without doc update
git log --merges --since="24 hours ago" --format="%H" | while read sha; do
git diff "${sha}^" "$sha" | grep -E "^\+.*(export function|export class|def |public )" | \
grep -v "test\|spec\|__" | grep -v "^+++"
done | head -20
# Check if corresponding docs were updated in the same merge
git log --merges --since="24 hours ago" --format="%H" | while read sha; do
HAS_CODE=$(git diff "${sha}^" "$sha" --name-only | grep -v "\.md$" | wc -l)
HAS_DOCS=$(git diff "${sha}^" "$sha" --name-only | grep "\.md$" | wc -l)
[ "$HAS_CODE" -gt 0 ] && [ "$HAS_DOCS" -eq 0 ] && git log -1 --format="%s" "$sha"
doneStep 6 — Score and prioritize cleanup items
For each item found, assign:
- Risk if ignored: High (flag blocks release, dead code causes confusion) / Medium / Low
- Effort: Small (< 1h) / Medium (1–4h) / Large (> 4h)
- Suggested action: fix-it-now / open-issue / defer
Step 7 — Report and optionally open issues
POST-MERGE CLEANUP — since 2026-06-29 (3 merges scanned)
TODOs Added (3)
src/payments/processor.ts:142 TODO: Remove legacy retry path after v2 rollout
Risk: Medium | Effort: Small | → open issue (link to PR #1245)
src/auth/token.ts:88 FIXME: Hardcoded 30s timeout, make configurable
Risk: Low | Effort: Small | → open issue
src/api/routes.ts:23 HACK: Temporary workaround for rate limit bug
Risk: High | Effort: Medium | → open issue + priority:high label
Feature Flags (1)
src/features/search-v2.ts FEATURE_SEARCH_V2 now hardcoded true — remove old path?
Risk: Low | Effort: Medium | → suggest cleanup after 2 sprint soak
Documentation Gaps (2)
PR #1243 added 3 new API endpoints with no doc update
Suggested: update docs/api/ for GET /v2/search, POST /v2/index, DELETE /v2/cache
PR #1241 changed auth flow — README.md authentication section is now stale
No dead code detected in recent merges.
Issues to open (if approved): 3 | Defer: 2
Run with --create-issues to open GitHub issues for approved items.Step 8 — Optionally create issues
# With --create-issues flag, open GitHub issues for High/Medium items
gh issue create \
--title "cleanup: Remove legacy retry path in payments/processor.ts (from PR #1245)" \
--body "TODO added in PR #1245 at src/payments/processor.ts:142. Remove after v2 rollout is stable." \
--label "tech-debt,cleanup"Edge Cases
- No recent merges: "No merges in the last 24h" — exit cleanly.
- Non-GitHub repo: Use
git log --mergesonly; skip PR-specific steps. - Large diff: Process first 50 changed files; note if truncated.
- TODOs that were removed (not added): Do not flag — that's already done cleanup work.
Token Optimization
Expected range: 400–1,200 tokens; 50–100 tokens (no recent merges, early exit)
Patterns used: Bash (git log, gh CLI, grep), git diff scope (recent merges only), early exit (no merges), progressive disclosure (count summary → item list → issue creation on request)
Early exit: No merges in the target window → single-line report and exit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

