finishing-a-development-branch
Complete a development branch before merge — verify tests pass, update documentation, ensure quality gate passes, and prepare a clean PR.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- finishing-a-development-branch
- description
- Complete a development branch before merge — verify tests pass, update documentation, ensure quality gate passes, and prepare a clean PR.
03 SKILL.md 正文
Finishing a Development Branch
Complete all final steps before merging a feature branch.
Announce at start: "I'm using the finishing-a-development-branch skill."
Checklist (Complete in Order)
1. Verify Tests Pass
npm test # or pytest, go test, cargo test
npm run test:coverage
- All tests must pass (no skips, no TODOs in critical paths)
- Coverage must be ≥ 80%
- If tests fail → stop and fix before continuing
2. Verify Build
npm run build # or go build ./..., cargo build --release
npx tsc --noEmit
- Build must succeed with zero errors
3. Quality Gate
- Run
/quality-gate(code review + security review in parallel) - Block MUST be resolved before merge
- Warn can merge with documented issue
4. Clean Up
- Remove all
console.logand debug statements - Remove all commented-out code
- Remove all TODO/FIXME without issue references
5. Update Documentation
- Update CLAUDE.md or README.md if setup changed
- Run
doc-updateragent if codemaps are out of date - Update CHANGELOG if project uses one
6. Prepare PR
git log --oneline [base-branch]..HEAD # Review all commits
git diff [base-branch]...HEAD # Review all changes
Write PR body with:
- Summary (3-5 bullet points of what changed and why)
- Test plan (checkboxes for manual verification steps)
- Screenshots if UI changed
7. Final Commit
- All changes staged and committed
- Commit message follows conventional format
- Branch is up to date with base
Hard Rules
- Never merge with failing tests
- Never merge with CRITICAL review findings
- Never merge to main/master directly (use PR)
- Never skip the quality gate
The branch is done when every checkbox above is checked.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.