finishing-a-development-branch
Workspace override — redirects all branch completion to /sync pipeline which enforces CHANGELOG, memlog, audit, and PR creation gates.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-11-14
- Stars
- ★ 25
- Forks
- 9
01 前言 Front Matter
- name
- finishing-a-development-branch
- owner
- pm
- scope
- common
- status
- active
- version
- 1.0.2
- triggers
- [ "finish branch", "complete work", "wrap up", "finishing a development branch", "merge branch", "create PR", "push and PR" ]
- description
- Workspace override — redirects all branch completion to /sync pipeline which enforces CHANGELOG, memlog, audit, and PR creation gates.
- last_reviewed
- 1781308800000
03 SKILL.md 正文
Finishing a Development Branch (Workspace Override)
This workspace overrides the global
finishing-a-development-branchskill.
Why this override exists
This workspace enforces a single PR creation path via /sync to guarantee:
- CHANGELOG.md entry exists before committing
- Session memlog is written to
memory/YYYY-MM-DD.md bun scripts/audit.tspasses before any push- Branch is named
pr/YYYYMMDD-HHMMSS-slugfor traceability
The global skill's Option 2 (push without commit) bypasses CHANGELOG and memlog requirements.
What to do instead
Always use /sync to complete work and create a PR:
/sync "type: description of what changed"
Examples:
/sync "feat: add user authentication"
/sync "fix: resolve null pointer in payment flow"
/sync "docs: update API reference"
The /sync pipeline handles everything:
- Writes session entry to
memory/YYYY-MM-DD.md - Updates
memory/MEMORY.mdindex - Verifies CHANGELOG.md has an entry (blocks if missing — run
/changelogfirst) - Runs
bun scripts/audit.ts(blocks on failure) - Creates
pr/date-slugbranch, commits, pushes, opens GitHub PR
Never use --no-verify
git commit --no-verify and git push --no-verify are forbidden in this workspace.
They bypass secret scanning (gitleaks) and all quality gates.
04 同仓库更多 Skills
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.
i18n-layout
Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL/bidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF/BOM issues surface.