Systematic Code Refactoring
luongnv89/claude-howto
Guides refactoring in phases based on Martin Fowler's method: research, test coverage check, planning and small tested steps, with your approval at each phase.
Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities.
Install Post Merge Scan
$ npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cobusgreyling/loop-engineering post-merge-scan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/starters/post-merge-cleanup-opencode/skills/post-merge-scan .claude/skills/post-merge-scan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "post-merge-scan" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/post-merge-cleanup-opencode/skills/post-merge-scan into .claude/skills/post-merge-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-merge-scan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cobusgreyling/loop-engineering/tree/main/starters/post-merge-cleanup-opencode/skills/post-merge-scanType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cobusgreyling/loop-engineering post-merge-scan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/starters/post-merge-cleanup-opencode/skills/post-merge-scan .agents/skills/post-merge-scan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "post-merge-scan" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/post-merge-cleanup-opencode/skills/post-merge-scan into .agents/skills/post-merge-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-merge-scan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cobusgreyling/loop-engineering post-merge-scan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/starters/post-merge-cleanup-opencode/skills/post-merge-scan .cursor/skills/post-merge-scan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "post-merge-scan" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/post-merge-cleanup-opencode/skills/post-merge-scan into .cursor/skills/post-merge-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-merge-scan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cobusgreyling/loop-engineering.git --path starters/post-merge-cleanup-opencode/skills/post-merge-scan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cobusgreyling/loop-engineering post-merge-scan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/starters/post-merge-cleanup-opencode/skills/post-merge-scan .gemini/skills/post-merge-scan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "post-merge-scan" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/post-merge-cleanup-opencode/skills/post-merge-scan into .gemini/skills/post-merge-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-merge-scan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cobusgreyling/loop-engineering post-merge-scanInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/starters/post-merge-cleanup-opencode/skills/post-merge-scan .github/skills/post-merge-scan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "post-merge-scan" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/post-merge-cleanup-opencode/skills/post-merge-scan into .github/skills/post-merge-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-merge-scan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cobusgreyling/loop-engineering post-merge-scan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cobusgreyling/loop-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/starters/post-merge-cleanup-opencode/skills/post-merge-scan .opencode/skills/post-merge-scan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "post-merge-scan" agent skill from https://github.com/cobusgreyling/loop-engineering/tree/main/starters/post-merge-cleanup-opencode/skills/post-merge-scan into .opencode/skills/post-merge-scan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-merge-scan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
post-merge-scan- GitHub stars
- 11k
- Token cost
- ~208 tokens
- SKILL.md length
- 79 words
- Files
- 1
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- MIT
At a glance
Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities.
- Tasks that involve Technical debt
- SKILL.md covers Scan Sources, Classification, Output and Rules
- Calls git
What it does
Post Merge Scan is an agent skill from cobusgreyling/loop-engineering. Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities. Produces a prioritized fix list.
Its SKILL.md is about 210 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Technical debt. The repository describes itself as: Practical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny)… The licence is MIT.
When your agent uses it
- Tasks that involve Technical debt
Example prompts
- “/post-merge-scan”
What it can do on your machine
Read from SKILL.md and the folder at commit e766228. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Post Merge Scan loads about 208 tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 79 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cobusgreyling/loop-engineering at commit e766228, republished under its MIT licence (© cobusgreyling). 79 words, ~208 tokens.
Download SKILL.mdSave it as
.claude/skills/post-merge-scan/SKILL.md (or your agent's skills folder).- name
- post-merge-scan
- description
- Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities. Produces a prioritized fix list.
- user_invocable
- true
Post-Merge Scan Skill
You are a post-merge cleanup agent. Scan recent merges for follow-up work.
Scan Sources
- Recent commits and PRs merged to main
git diff HEAD~10for left-behind debug code- TODO/FIXME/HACK comments in changed files
- Lint warnings introduced by recent changes
Classification
- Small fix: doc/comment/lint/debug — auto-fix candidate
- Architectural debt: ticket for human
- Denylist path: escalate to human
Output
Update post-merge-state.md with prioritized cleanup list.
Rules
- Run off-peak (evening).
- Never auto-fix architectural debt.
- Max 2 fix attempts per run.
© cobusgreyling, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in starters/post-merge-cleanup-opencode/skills/post-merge-scan of cobusgreyling/loop-engineering.
Open the folder on GitHubat commit e766228
Compare with similar skills
Post Merge Scan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Post Merge Scan this skillcobusgreyling/loop-engineering | 11k | — | ~208 | Automated safety check: Pass | MIT | |
| Systematic Code Refactoringluongnv89/claude-howto | 42k | — | ~3k | Automated safety check: Pass | MIT | |
| Code Simplification for ego-litecitrolabs/ego-lite | 17k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Code Refactoring Workflowluongnv89/claude-howto | 42k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 381 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Ponytail Debt LedgerDietrichGebert/ponytail | 160k | — | ~453 | Automated safety check: Pass | MIT |
Similar skills
Code Simplification for ego-lite
citrolabs/ego-lite
Finds and implements evidence-backed simplifications in the ego-lite repository, such as dead code, duplicated state and speculative abstractions, without hiding behavior changes.
Code Refactoring Workflow
luongnv89/claude-howto
Guides systematic, test-backed refactoring in the style of Martin Fowler, moving through research, planning and small incremental changes with your approval at each phase.
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Ponytail Debt Ledger
DietrichGebert/ponytail
Collects every ponytail: comment in a codebase into one debt ledger, flags shortcuts with no upgrade trigger and reports without changing any files.
FIXME Resolver
tailcallhq/forgecode
Finds every FIXME comment in a codebase, groups related ones across files into one task, implements the work they describe and removes the comments once it is done.
More from cobusgreyling/loop-engineering
All 21 skills in this repoInstall Loop Engineering
cobusgreyling/loop-engineering
Installs Loop Engineering into a project through the single @cobusgreyling/loop CLI, scaffolding a report-only loop and a readiness score.
Loop Constraints Enforcer
cobusgreyling/loop-engineering
Loads a project's loop-constraints.md before any other action and blocks pushes, edits or merges that violate the rules it defines.
Release Notes Drafter
cobusgreyling/loop-engineering
Turns a structured list of changes from changelog-scan into a categorized, user-facing release notes draft file, and never publishes anything.
Issue Triage Loop
cobusgreyling/loop-engineering
Scans open GitHub issues and discussions, flags duplicates, scores priority and proposes labels into issue-triage-state.md without ever labeling or closing.
Loop Triage Report
cobusgreyling/loop-engineering
Turns CI failures, open issues, recent commits and chat threads into a prioritized markdown report that an automation loop can act on without inventing architecture work.
Loop Token Budget Guard
cobusgreyling/loop-engineering
Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.
Related
Categories
Questions about Post Merge Scan
What does Post Merge Scan do?
Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities. Post Merge Scan is an agent skill from cobusgreyling/loop-engineering. Scan recent merges to main for tech debt, TODOs, debug code, and small cleanup opportunities.
When should I use Post Merge Scan?
Post Merge Scan fits situations like: tasks that involve Technical debt.
How do I install Post Merge Scan in Claude Code?
Run `npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a claude-code`. Or copy the skill folder (starters/post-merge-cleanup-opencode/skills/post-merge-scan in cobusgreyling/loop-engineering) into .claude/skills/post-merge-scan in your project. Claude Code loads it when a task matches its description.
How do I install Post Merge Scan in Codex?
Run `npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a codex`. Or copy the skill folder (starters/post-merge-cleanup-opencode/skills/post-merge-scan in cobusgreyling/loop-engineering) into .agents/skills/post-merge-scan in your project. Codex loads it when a task matches its description.
Can I use Post Merge Scan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cobusgreyling/loop-engineering --skill post-merge-scan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-merge-scan, .gemini/skills/post-merge-scan, .github/skills/post-merge-scan and .opencode/skills/post-merge-scan in your project.
What does Post Merge Scan need to run?
Going by SKILL.md and its folder, Post Merge Scan needs the command-line tools its instructions call (git).
Does Post Merge Scan access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Post Merge Scan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Post Merge Scan use?
Post Merge Scan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Post Merge Scan use?
About 208 tokens (SKILL.md is roughly 832 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Post Merge Scan?
Skills that share tags, products or a category with Post Merge Scan: Systematic Code Refactoring (luongnv89/claude-howto, 42k stars), Code Simplification for ego-lite (citrolabs/ego-lite, 17k stars), Code Refactoring Workflow (luongnv89/claude-howto, 42k stars) and Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 381 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Post Merge Scan?
cobusgreyling (a GitHub user) maintains it in cobusgreyling/loop-engineering, which has 11,448 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 10, 2026.
Source: cobusgreyling/loop-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.