メニュー
Git branching, commit, and PR procedures. Use when creating branches, making commits, or opening pull requests. Enforces branch naming, commit message format, and PR rules.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | git-flow |
| license | MIT |
| description | Git branching, commit, and PR procedures. Use when creating branches, making commits, or opening pull requests. Enforces branch naming, commit message format, and PR rules. |
All development follows the project's Git Workflow.
Full spec: see GIT_WORKFLOW.md in the project's standards (.agents/ or skeleton).
Before writing any code, create a branch.
Direct-Commit Mode check (first): Read .memory/CONFIG.md. If Direct-Commit Mode | on, OR the user's current request is prefixed with direct:, verify the change qualifies (see refusal list in docs/AUTONOMY-MODES.md):
[DEFAULT_BRANCH]. Surface the DIRECT-COMMIT MODE ACTIVE — committing directly to [DEFAULT_BRANCH] (no PR). banner. Jump to Commit Messages.Refusing Direct-Commit Mode — <reason>; switching to full flow. and continue with branch creation as normal.Otherwise (mode off, or user did not prefix direct:) — proceed with branch creation:
[DEFAULT_BRANCH] and pull latest:
git checkout [DEFAULT_BRANCH] && git pull
BOARD-XXXX-kebab-descriptiondebt-id-kebab-descriptiongit checkout -b <branch-name>
[DEFAULT_BRANCH].[BOARD-XXXX] short description[DEBT-ID] short descriptiongit log — one bug fix, one new function, one refactor pass, one doc update. Not one giant end-of-workflow commit.Commit granularity: line stating the chosen strategy so it stays visible across steps.When implementation is complete.
Direct-Commit Mode check (first): If Direct-Commit Mode was active for this task (verified in Branch Creation), skip this entire section. The commit was made directly to [DEFAULT_BRANCH]; there is no feature branch to push and no PR to open. Push directly:
git push origin [DEFAULT_BRANCH]
Then jump to the end-of-turn summary. Task-completion still runs in full.
Otherwise — proceed with the PR flow:
git push -u origin <branch-name>
[DEFAULT_BRANCH] with:
[BOARD-XXXX] short description or [DEBT-ID] short descriptionPR #N: <url> or just <url>. Never comma-separate or pack into a paragraph; the user needs to click each independently. When a turn opens multiple PRs (memory branch + main branch is the common case), list both:
PR #42 (memory): https://github.com/.../pull/42
PR #43 (main): https://github.com/.../pull/43
agentskel has two modes that reduce friction during agent work, toggled in .memory/CONFIG.md:
[DEFAULT_BRANCH]. One-shot prefix direct: available.Both modes are independent and composable. See docs/AUTONOMY-MODES.md for the full procedure, boundary definitions, refusal cases, and how the two modes interact.
When Direct-Commit Mode is active for the current task, the agent MUST surface a banner BEFORE any commit:
DIRECT-COMMIT MODE ACTIVE — committing directly to [DEFAULT_BRANCH] (no PR).
Surfacing is non-optional — ceremony-skipping must be visible.
When the user confirms a PR has been merged (says "merged", "done", or equivalent), the agent must execute cleanup BEFORE starting any next task. This is non-optional — leaving stale local/remote branches around accumulates and breaks the next branch creation.
git branch
output — never guess).git checkout [DEFAULT_BRANCH]
git pull origin [DEFAULT_BRANCH]
git branch -d <branch-name>
-d fails, report it to the user — do not force-delete with -D without
explicit instruction.git remote prune origin
git branch -a should show only the default branch and any other legitimate long-lived branches (e.g. ai-memory). No leftover feature branches.Gate: do not begin the next task until the cleanup completes and git branch -a is clean.
For long feature runs or parallel branch work, use an isolated worktree instead of
working directly in the main repo. See using-git-worktrees skill for full procedure.
Quick reference:
# Create (branch must already exist)
git worktree add "../$(basename $(git rev-parse --show-toplevel))-<branch-name>" <branch-name>
# Cleanup after merge
git worktree remove "../<repo>-<branch-name>"
git branch -d <branch-name>
Gate: Do not write any application code until a branch has been created. Do not consider a task shipped until a PR is open.
Session initialization procedure. Checks memory mount, reads all required memory files, validates skeleton version, checks dependency freshness, and surfaces alerts. Must be executed at the start of every session before any other work.
When writing, modifying, or reviewing application code. Provides code quality standards, SOLID principles, design philosophy, and platform-specific implementation guidance.
When a single new person joins the team. Use when `.memory/TEAM.md` already exists and you need to append one member (with roles, optional module assignments, and optional Jira account ID) without touching the rest of the roster.
When adding a new platform (subdir with its own git repo) to an existing workspace dispatcher. Runs setup-skeleton in the subdir and updates the workspace config and dispatcher AGENTS.md.
When reading or writing to Jira tickets or Confluence pages via MCP tools. Use before any Jira transition, ticket creation, or Confluence page update to avoid common failure modes.
When the user wants to think through a feature idea, explore edge cases, or produce a technical spec before implementation. Use before develop-feature to prevent mid-implementation surprises.