Finishing a development branch
Skill roronoazoroshao369/vibe-coding-os/skills/core/finishing-a-development-branch
Vibe Coding OS — Claude/Codex/Cursor skill framework with 139 skills, 111 commands, 95 templates, 22 tracked sources, 28/28 validation gates PASS. Quality Shield, Engineering Discipline Pack, plugin marketplace.From the repository description
npx -y skills add roronoazoroshao369/vibe-coding-os --skill finishing-a-development-branchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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.
SKILL.md
1.7 KB, 318 tokens by cl100k_base, as published. Nobody here has run it
Skill: Finishing a Development Branch
Purpose
Close a branch cleanly with verified status, review readiness, attribution hygiene, memory notes, and clear next actions.
When to use
Use at the end of a feature/bugfix/reference-integration branch before PR, merge, handoff, or cleanup.
Inputs
Branch name, diff summary, spec/plan, validation output, review state, attribution obligations, memory/follow-up needs, and cleanup constraints.
Workflow
- Inspect
git status, branch name, and recent commits. - Confirm the diff matches the accepted scope and no generated or upstream clone artifacts are staged accidentally.
- Run or summarize final validation and note exact failures/limitations.
- Ensure review feedback is handled or explicitly deferred.
- Update memory, changelog, attribution, or reference notes when the work created durable knowledge.
- Prepare a final handoff or PR summary with changed files, checks, risks, assumptions, and cleanup tasks.
Outputs
A branch-finish report or PR-ready summary with clean status, validation evidence, review state, attribution state, and follow-ups.
Failure modes
- Finishing with unreviewed unrelated changes.
- Claiming completion while validation is unknown.
- Forgetting attribution or reference changelog updates.
- Leaving branch/worktree cleanup ambiguous.
Verification checklist
- Working tree and branch status are known.
- Diff matches scope.
- Final checks are reported honestly.
- Review, attribution, and memory obligations are addressed.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.