メニュー
Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Turn the current conversation context into a spec and submit it as a GitHub issue. Use when the user wants to create a spec from the current context, or invokes `/create-spec`.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
Break a plan, spec, or the current conversation into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Ultra-compressed communication mode. Cuts output tokens 65% (measured) by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
An extremely strict maintainability audit for abstraction quality, giant files, and spaghetti-condition growth. Use for a deep code quality review, code quality audit, or harsh maintainability review.
| name | commit-guidelines |
| description | Guidelines for creating git commits. Use when making commits, staging changes for commit, or deciding how to split changes across commits. |
| user-invocable | false |
git log shows the repo follows a different conventionadd, not added/adds)Format: <type>: <summary>
Types:
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
chore | Maintenance tasks, dependencies, config |
refactor | Refactoring (no behavior change) |
perf | Performance improvement |
docs | Documentation only |
test | Test additions or corrections |
style | Code formatting (no logic change) |
Skip the body when the subject is self-explanatory. Add a body only for:
Wrap body text at 72 characters.
Append ! after the type and add a BREAKING CHANGE: footer:
feat!: remove deprecated v1 endpoints
BREAKING CHANGE: v1 endpoints no longer available
Reference GitHub issues in the commit footer:
Fixes #123 — closes the issue when mergedRefs #123 — links without closingfeat: add OAuth2 login flow
fix: handle null response in user endpoint
The API could return null for deleted accounts, causing a crash.
Fixes #42
refactor: extract validation logic to shared module