メニュー
Git operations enforcer - manages branches, commits, and pull requests with strict naming conventions and quality gates
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Trace the second-, third-, and nth-order consequences of a decision, change, or plan — the effects of the effects — so thinking doesn't stop at the obvious first-order outcome. Use when the user asks "what are the consequences of X", "think this through", "second-order effects", "n order consequences", "what could this cause downstream", or before committing to a significant decision (technical, product, organizational, personal).
Quiz the user on whether they actually understand a code change before it ships. Generates a short literate explainer of a diff, then administers five comprehension questions that test how the change works — not requirements, not trivia. Use before opening a PR, before merging, when reviewing someone else's PR, or when the user says "quiz me on this", "do I understand this change", "code quiz", "gate this PR", or wants to check comprehension of AI-written code.
Bruno API client skill — .bru file format, JavaScript API reference, authentication patterns, testing with Chai.js, and Git-first collection management.
Review feature code against DDD and hexagonal architecture principles. Validates domain entities, value objects, use cases, adapters, folder structure, file naming, and test placement.
Create Phase 0 documentation for a new feature. Generates docs folder structure with plan.md, glossary.md, business-logic.md, architecture.md, errors.md, questions.md, and adr/ folder. Use before any code is written.
Teaches Helix editor by analyzing the user's existing configuration, explaining keybindings and LSP setup, and answering questions. Use when the user asks about Helix, their helix config, keybindings, LSP setup, themes, or wants help setting up or learning Helix. Also triggers on "helix keybindings", "explain my helix config", "helix setup", "learn helix", or "hx config".
| name | git-operations |
| description | Git operations enforcer - manages branches, commits, and pull requests with strict naming conventions and quality gates |
| user_invocable | true |
| arguments | [{"name":"operation","description":"Operation to perform: branch, commit, pr. Defaults to contextual detection.","required":false}] |
Expert automation for maintaining clean, atomic, and traceable Git workflows. Guardian of Git quality — every branch, commit, and pull request meets exacting standards.
See these reference files for details:
branch-rules.md — Branch naming conventions, series branches, validation stepscommit-rules.md — Quality gates, atomicity checks, Conventional Commits formatpr-rules.md — PR creation, title format, template structure, metadata"As small as possible, but complete."
Every change must be:
Pattern: dld-<ticketNumber>/<Short-Description>
dld-123/Add-Autopay-Summary
dld-57/Fix-Lease-Balance
Series branches add suffix: dld-123/Feature-Name-2, dld-123/Feature-Name-3
<type>(<scope>): <subject>
Types: feat, fix, refactor, test, docs, style, chore, perf, ci, build
DLD-<number> <Description>
pnpm lint:fix
pnpm typecheck
pnpm test:server:unit
pnpm test:server:integration # if relevant
.unit.test.ts, .integration.test.ts