メニュー
Pointer — protected-branch commit/merge policy is owned by the git-branch.md rule and enforced mechanically by the branch-guard hook + husky pre-commit. Consult before committing when on main/master/develop.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Pipeline for delegating one large mechanical change to a worker under a hard green-or-report gate — specify, dispatch mechanical-refactor-worker, independently re-verify the green claim, hand the working-tree diff to pr-review-reviewer, then commit. Route-only: it does no editing and forms no verdict. Use when delegating a big decision-free change on your own working tree.
Procedure for running multiple independent backlog items in parallel via worktree-isolated subagents with zero merge conflicts — partition file ownership before spawning, isolate each implementer in its own worktree, sequence overlapping work behind occupants, one coherent self-verified PR per agent, and serial orchestrator merge. Use when executing 2 or more independent items concurrently.
Thin router for the doc-vs-code architecture conformance audit (GATE-CONFORMANCE). Routes to the mechanical conformance scan plus the architecture-refresh agent loop (architecture-conformance-auditor / architecture-auditor + fixers), which own the audit behavior natively. Use before a release, after cross-package work, or when GATE-CONFORMANCE runs.
Router for the mandatory post-implementation sequence — SPEC sync, build/test, README, commit/PR, publish, content/ docs, docs deploy. Each step's detail lives in its owning skill/rule; this file only fixes the order and the gates. Execute automatically after implementation work; do not wait for the user to request it.
Orchestrator for the spec document gate pipeline. Reads current status from frontmatter, determines the next gate, invokes backlog-writer or backlog-gate-guard, and updates frontmatter status on PASS. Does nothing else.
Mandatory verification loop after any SPEC.md or contract document change. Compares spec against implementation code, fixes code to match spec, repeats until zero discrepancies, then runs regression tests. Spec is always the source of truth — never modify the spec within this workflow.
| name | branch-guard |
| description | Pointer — protected-branch commit/merge policy is owned by the git-branch.md rule and enforced mechanically by the branch-guard hook + husky pre-commit. Consult before committing when on main/master/develop. |
The policy (branch-first, protected branches, merge-target = fork origin, release merges,
--delete-branch prohibition) is owned by git-branch.md. Do not
restate it — read it there.
AGENTS.md > "Git Operations".claude/hooks/branch-guard.sh) — blocks git commit/push/merge
Bash tool calls on main/master/develop before they run. It parses the command string, so a
commit whose message breaks its regex extraction (multi-line, embedded quotes) can slip past —
which is exactly how a release-record commit once landed directly on main (2026-06-14)..husky/pre-commit — runs for EVERY commit regardless of how it is invoked; the
robust backstop for what the parsing layer misses.Exceptions (both layers): a merge in progress (.git/MERGE_HEAD), or the explicit overrides
ALLOW_PROTECTED_COMMIT=1 (husky) / BRANCH_GUARD_ALLOW_MAIN_MERGE=1 (Claude hook) for
user-approved release automation. Branch-first applies even to one-line doc commits — always
branch → commit → PR.
If the hook fires (or you notice you are on a protected branch): stop, propose a conventional
branch name (feat|fix|refactor|docs|chore/<scope>-<desc>), get user approval, then
git checkout -b and continue — subsequent commits in the same task stay on that branch without
re-asking.