القائمة
Complete a development branch before merge — verify tests pass, update documentation, ensure quality gate passes, and prepare a clean PR.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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. |
Complete all final steps before merging a feature branch.
Announce at start: "I'm using the finishing-a-development-branch skill."
npm test # or pytest, go test, cargo test
npm run test:coverage
npm run build # or go build ./..., cargo build --release
npx tsc --noEmit
/quality-gate (code review + security review in parallel)console.log and debug statementsdoc-updater agent if codemaps are out of dategit log --oneline [base-branch]..HEAD # Review all commits
git diff [base-branch]...HEAD # Review all changes
Write PR body with:
The branch is done when every checkbox above is checked.
Systematic architecture review workflow. Use before major feature work on an unfamiliar or inherited codebase, before scaling milestones, or as a periodic health check. Maps the system as-built (not as-documented), dispatches parallel specialist reviews, and produces an evidence-backed findings report with severity verdicts.
The meta-skill. Loaded at every session start. Defines which A Team skills and agents MUST be used for which situations. If a skill or agent applies, you do not have a choice — you must use it.
Conversational onboarding for A Team. Detects ROADMAP.md, extracts context, generates INIT.md without requiring technical knowledge. Invoked automatically by the orchestrator when INIT.md is missing.
Root cause analysis using the Five Whys technique. Use when a bug persists despite surface fixes, a failure recurs, or a process keeps breaking. Ensures the fix targets the root, not the symptom.
Hard gate before implementing any API endpoint or service interface. Requires a written, reviewed contract (OpenAPI 3.x, protobuf, or GraphQL schema) before any implementation code is written. Prevents breaking changes, misaligned clients, and undocumented behaviour.
Use BEFORE any creative work — creating features, building components, adding functionality. Explores user intent, requirements, and design before implementation. Hard-gated: no code until user approves the spec.