finishing-a-development-branch
What it claims to do
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
What we found · 4
- Trigger is too broadmediumWords like "all" make it fire everywhere and fight other skills for the same task — the #1 cause of conflicts.
- Bloated: high token costmedium~1,703 tokens on every single call. Compress instructions and trim examples.
- Embedded shell script blockmediumShips runnable command-line scripts. Not necessarily bad, but must be sandboxed and reviewed.
- Repeated contentlow~4 duplicate lines detected; de-duping is free token savings.
What its scripts can do
| medium | Writes / deletes files |
Conflicts with · 8
| cloudflare-one | shadow | guid, work |
| brainstorming | shadow | work, implementation |
| using-git-worktrees | shadow | implementation, work |
| verification-before-completion | shadow | complete, work |
| doc-coauthoring | shadow | structur |
| mcp-builder | shadow | integrate |
| skill-creator | shadow | test |
| webapp-testing | shadow | test |
If you have both installed, they compete for the same triggers — the top cause of an agent picking the wrong skill.
One command grades every skill in your Claude Code / Codex — safety, token bloat, and conflicts, 100% locally.
npx skillmoo scan
Grade computed 2026-07-13 · rubric static-v1. Efficacy shown only when measured on a labeled model + task suite — never invented.
Add this independent grade to the skill's README — the badge links back to this rating and updates when we re-grade.
[](https://skillmoo.com/skill/finishing-a-development-branch/)