Finishing a development branch

Skill wfprieto/wcbs-build-kit/skills/finishing-a-development-branch

Use when implementation tasks are complete and the branch or worktree needs final verification, merge/PR/keep/discard decision support, cleanup, and release-readiness evidence.From its SKILL.md

Install

npx -y skills add wfprieto/wcbs-build-kit --skill finishing-a-development-branch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 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

2.8 KB, as published. Nobody here has run it

Finishing A Development Branch

Choose an explicit finish path only after the branch proves its claimed behavior. “The implementation looks complete” is not a merge decision.

Process

git status --short --branch
git log --oneline --decorate origin/main..HEAD
git diff --check origin/main...HEAD

Then complete, in order:

Run every verification command named by the plan and list anything Not Run.
Re-read the complete origin/main...HEAD diff for scope, user-file safety, generated artifact drift, secrets, and weakened assertions.
Run the final review path. If a runtime has no independent reviewer, label the fresh-context substitute as degraded independence.
Check release gates, hosted CI requirements, rollback trigger, and support claims. A local pass does not replace a required hosted or authenticated runtime check.
Select exactly one path: open PR, merge after verified protected CI, retain branch for iteration, or discard after explicit approval.

Worked Example

npm run release-check
git diff --check origin/main...HEAD
git status --short

If all local checks pass but the Windows matrix is still queued, the correct status is CONDITIONAL PASS, not merge-ready. Keep the branch and wait for the required hosted evidence. If a runtime clean-session test is Blocked, lower the adapter’s verified support label rather than weakening the test.

Cleanup Rules

Never remove a worktree you did not create or cannot identify as yours.
Never delete a branch until merge/PR state and remote protection are known.
For a discard path, verify from outside the worktree, preserve the commit or patch needed for recovery, remove the worktree, then run git worktree prune.
For a PR path, retain the worktree until review and re-review are complete.

Final Receipt

Branch and immutable head:
Verification run / not run:
Review and re-review state:
Release-gate status:
Chosen finish path:
Rollback trigger:
Evidence state and APIVR verdict:
Single next action: