メニュー
Governance rules and stack definitions. Source `.md` files install as path-scoped Claude rules in `.claude/rules/`. Use for adding rules, editing stacks, or install and sync.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | aitk-governance |
| description | Governance rules and stack definitions. Source `.md` files install as path-scoped Claude rules in `.claude/rules/`. Use for adding rules, editing stacks, or install and sync. |
Read .claude/context/governance.md for system overview, numbering scheme, and stack structure before editing.
.claude/context/governance.md for the numbering ranges before picking a number for a new rule.prompts/governance-rules.md for frontmatter, heading style, and bullet conventions when writing a new rule file.strip_frontmatter, build_rules_payload, and rule_subdir live in scripts/lib/gov.sh. Do not duplicate.aitk gov install <stack> <target> writes .claude/rules/<subdir>/<rule>.md as a passthrough copy. Source files carry the Claude shape directly, so the install copies the .md file as-is and preserves subdirectories.aitk gov sync diffs .claude/rules/ against source. It also removes any stale .claude/GOV.md left over from the retired build.aitk gov build produces a single concatenated paste-payload at .claude/.tmp/gov/rules.md from .claude/rules/..toml in governance/stacks/, set extends, list rule names without .mdWhen adding a rule:
rules array in governance/stacks/*.toml if it belongs to a stackWhen adding a stack:
.toml in governance/stacks/, set extends, list rulesAfter writing or revising a rule, audit each bullet against the checklist. Trigger phrases: "audit this rule", "review the governance rule", "is this rule worth keeping".
.claude/skills/aitk-governance/references/rule-audit.md for the criteria and output shape..claude/context/governance.md: system overview, numbering scheme, install vs sync vs build, stacksprompts/governance-rules.md: conventions for writing rule filesPulls review findings and CI status on the current branch's open PR, fixes each in the working tree, refreshes any stale `.claude/` docs, replies with a summary comment, and pushes a follow-up commit. The worker's return leg after `claude-pr-review`. Use when asked to "address the review", "fix the PR comments", "respond to review", or after an orchestrator posts findings. Do NOT use to write a review. That is `claude-pr-review`.
Ships a small self-review edit on the current PR branch by staging, committing, pushing, and syncing the open PR, replying on the PR when it carries review comments. Use when asked to "ship a followup", "push the PR fix", "followup", or "commit and push this small change". Do NOT use when there is no open PR for the branch (use git-ship instead).
Claude skill structure and authoring rules
Chains implement → verify → review → ship after a feature plan is approved. Reads the plan for the current branch, runs the full pipeline in one session, and stops on any failure or non-minor review finding. Use when asked to "autoship", "ship this feature end to end", or "run the chain". Do NOT auto-trigger. Requires an approved plan file.
Asserts the orchestrator role for the current session and holds the build loop, dispatching to the roadmap, feature, review, and worktree skills. Use when asked to "be the orchestrator", "run the orchestrator", "orchestrate this project", or to set up the control session for parallel feature builds. Do NOT build features or merge PRs in this session.
Reviews an open pull request from an independent session and posts findings as a review comment on the PR. Reads project docs and the roadmap for cross-feature context a self-review lacks. Use when asked to "review the PR", "review this feature's PR", "post a PR review", or acting as the orchestrator reviewing a worker's PR. Do NOT use to review local uncommitted changes. That is `claude-review`.