Finishing a development branch
Skill kimtth/agent-skill-100-lines-or-less/skills/finishing-a-development-branch
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill finishing-a-development-branchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: implementation is complete and you need to verify, summarize, and choose merge, PR, commit, or cleanup flow.
SKILL.md
1.1 KB, 199 tokens by cl100k_base, as published. Nobody here has run it
Goal: finish development work without losing verification or branch hygiene.
Workflow:
- Run the project's relevant tests before presenting completion options.
- Inspect git status, branch, worktree state, and uncommitted changes.
- Summarize what changed and what evidence passed.
- Present integration options: commit, open PR, merge, leave changes, or cleanup.
- Execute only the user's chosen option.
- Clean temporary branches/worktrees only when safe and approved.
If tests fail:
- show the failing command and failure count
- stop integration work
- fix or ask before proceeding
Git checks:
git status --short- current branch
- worktree vs normal checkout
- staged vs unstaged changes
Rules:
- do not merge, commit, or delete branches without explicit approval
- do not present PR/merge as ready until verification passes
- keep unrelated dirty work separate
- include residual risk in the final handoff