メニュー
Formulate precise, standard-compliant Git commit messages based on the conventional commits specification. Use when you are ready to execute `git commit`.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Designs, audits, and iteratively validates framework, platform, language, protocol, or runtime architectures by combining explicit requirements, mature theory, external-system research, executable prototypes, dogfooding, and cross-artifact reconciliation. Use when creating or redesigning an architecture, writing architecture specifications or ADRs, auditing an existing architecture against abstraction/completeness/orthogonality/extensibility, or planning a design for production implementation.
Update STATE.md — the lightweight cross-session "daily report" of project progress. Rewrite (never append) the current milestone/phase, what this session completed or changed, pitfalls worth reusing, the recommended next issues/tasks, and the filtered-and-inherited backlog of unfinished cross-session items. Use at the end of a working session, when wrapping up, or when invoked as /state.
Drive the Godot game engine from the command line with `gda`, an agent-first CLI with structured JSON output. Use when building, editing, or inspecting a Godot project — create/edit scenes, nodes, GDScript, resources, shaders, themes; run static analysis; export builds (all headless, no editor) — or to control a running game live (runtime scene tree, input simulation, screenshots, performance, runtime logs/errors) via the gda daemon. Use when the user mentions gda, Godot automation, headless Godot, or asks an agent to make/modify a Godot game. Always pass `--json` and read the single result object; run `gda --help` or `gda schema` to discover the full command surface.
Orchestrates parallel development by fanning out independent feature slices to subagents in isolated git worktrees, then merging them serially under an orchestrating agent — covers dependency decomposition, wave sizing, dispatch prompts, merge-conflict hazards, and the integration-test gate. Use when planning to parallelize implementation across multiple subagents/worktrees, split a task for concurrent agents, fan out feature slices, or merge several feature branches back together; or invoked as /subagent-worktree-parallel.
Check and repair consistency between GitHub issues and domain docs (CONTEXT.md, docs/adr/) after a requirement or technical decision changes — mechanical cross-reference integrity plus conversation-driven semantic staleness. Use when a decision or requirement was changed or discussed in the current session, when issues/docs may have drifted out of sync, when the user says "reconcile" / "sync issues and docs" / "check cross-references", or when invoked as /reconcile.
| name | git-conventional-commits |
| description | Formulate precise, standard-compliant Git commit messages based on the conventional commits specification. Use when you are ready to execute `git commit`. |
This skill enables the code agent to formulate precise, standard-compliant Git commit messages and branch names based on the Conventional Commits 1.0.0 specification. Adhering to this standard allows automated tools to parse commit histories, bump semantic versions (Major/Minor/Patch) accurately, and generate clean changelogs.
git commit.Every commit message must strictly follow this structural pattern:
<type>(<scope>): <subject>
<body>
<footer>
| Type | Definition | SemVer Impact |
|---|---|---|
feat | A new feature implemented in the codebase | Minor |
fix | A bug fix implemented in the codebase | Patch |
docs | Documentation only changes (e.g., markdown files) | None |
style | Changes that do not affect the meaning of the code (white-space, formatting, etc.) | None |
refactor | A code change that neither fixes a bug nor adds a feature | None |
perf | A code change that improves performance | None |
test | Adding missing tests or correcting existing tests | None |
build | Changes that affect the build system or external dependencies | None |
ci | Changes to CI configuration files and scripts | None |
chore | Other changes that don't modify src or test files (e.g., .gitignore) | None |
A breaking change must be indicated by an exclamation mark ! immediately after the type/scope, or by including BREAKING CHANGE: at the beginning of the footer. This triggers a Major version bump.
When resolving a tracked issue, the agent MUST reference the issue number in the footer using specific keywords (Fixes: #, Closes: #) to trigger GitHub's automated issue-closure workflows.
feat(auth): add JWT token expiration validation
Introduce an automated expiry verification check on the middleware layer
to automatically reject tokens older than 15 minutes.
fix(api): prevent null pointer exception during report export
Ensure that user profile data is properly validated before serialization
to prevent catastrophic crashes on empty profiles.
Fixes: #142
refactor(core)!: drop support for legacy v1 endpoint routes
The old v1 gateway endpoints have been deprecated for 6 months and are
now completely stripped out of the routing framework.
BREAKING CHANGE: Requests sent to `/api/v1/*` will now return a 404 error.
When creating a branch to work on an issue, use the type and issue number format:
git checkout -b fix/142-null-pointer-export