fork-dev-branch
Create a development branch for a given GitHub issue with standardized naming
Create a development branch for a given GitHub issue with standardized naming
Use when beginning implementation from a design plan - orchestrates branch creation, detailed planning, and hands off to execution with all necessary context
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when creating or updating CLAUDE.md files for projects or subdirectories - covers top-level vs domain-level organization, capturing architectural intent and contracts, and mandatory freshness dates
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Creates a git worktree for parallel feature development. Use after planning to prepare an isolated development environment with all necessary environment files.
Create a PR and automatically cleanup the worktree. Keeps local and remote branches intact.
Use when planning git branching strategies or managing branches for development. Helps create clear development narratives through effective branch organization and workflow patterns.
Use when planning commit strategies or determining when to commit changes. Helps developers commit early and often to tell the story of their development process.
Use when setting up CI/CD, implementing versioning, optimizing workflows, or managing releases with monorepo development workflows including version management, publishing, and team collaboration practices.
Guidelines for pull requests descriptions. Use when asked to create a PR, or decided to create one by yourself, or when asked to write/improve PR description.
Use when organizing complex CocoaPods libraries into subspecs. Covers modular architecture, dependency management between subspecs, and default subspecs patterns for better code organization and optional features.
Use when writing commit messages that clearly communicate changes and tell the story of development. Helps create informative, well-structured commit messages that serve as documentation.
Use when biome configuration including biome.json setup, schema versions, VCS integration, and project organization.
Atomic Commit helps create clean, atomic commits by analyzing changes, detecting mixed concerns, and ensuring each commit is a complete unit of work. Key words to detect are atomic, atomic commits, clean commits.
Use when creating temporary files, drafts, experiments, or any content that should not be committed to version control. Ensures proper placement in .claude/.scratch with gitignore configuration.
This skill should be used when the user asks to "write go", "golang", "go.mod", "go module", "go test", "go build", or works with Go language development. Provides comprehensive Go ecosystem patterns and best practices.
Branch completion workflow - guides merge/PR/cleanup decisions after implementation is verified complete.
Isolated workspace creation - creates git worktrees with smart directory selection and safety verification for parallel feature development.
Review reception protocol - requires technical verification before implementing suggestions. Prevents performative agreement and blind implementation.
This skill should be used when working with Graphite (gt) for stacked pull requests. Use when users mention gt commands, stack management, PR workflows, or when dealing with dependent branches. Essential for understanding stack navigation, branch relationships, and Graphite's mental model.
Write section/subsection prose into per-unit files under `sections/`, so each unit can be QA’d independently before merging into `output/DRAFT.md`. **Trigger**: subsection writer, per-section writing, split sections, sections/, 分小节写, 按章节拆分写作. **Use when**: `Approve C2` is recorded and evidence packs exist; you want evidence-first drafting without a monolithic one-shot draft. **Skip if**: `DECISIONS.md` approval is missing, or `outline/evidence_drafts.jsonl` is incomplete/scaffolded. **Network**: none. **Guardrail**: do not invent facts/citations; no ellipsis/TODO/placeholder leakage; keep citations subsection- or chapter-scoped (prefer subsection); H3 body files must not contain headings.
Initialize a new workspace by copying the standard artifact template (STATUS.md, CHECKPOINTS.md, UNITS.csv, DECISIONS.md + folders). **Trigger**: workspace init, initialize workspace, workspace template, 初始化 workspace. **Use when**: 启动任何 pipeline run(必须先有 workspace 工件与目录骨架)。 **Skip if**: workspace 已初始化且不希望覆盖既有文件(除非显式 `--overwrite`)。 **Network**: none. **Guardrail**: 不要修改 `.codex/skills/workspace-init/assets/` 模板;默认不覆盖已有文件。