メニュー
Write descriptive conventional commit messages that explain intent. USE FOR: committing changes; reviewing staged diffs; drafting commit messages; when the user asks to commit. DO NOT USE FOR: general coding; writing tests; deployment.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Step-by-step workflow for deploying this project. USE FOR: creating a new release; drafting release notes; classifying semver (patch, minor, major); publishing a version tag or GitHub Release; understanding the CI → CD → staging → production pipeline; knowing what triggers Docker image builds; checking deployment status. DO NOT USE FOR: general coding; writing tests; local development setup.
Guidance on using the project Makefile as the primary development interface. USE FOR: running tests, linting, formatting, security scans, or Docker commands; understanding which make target to use for a task; replacing raw commands with their make equivalents. DO NOT USE FOR: understanding the deployment pipeline; adding dependencies; writing documentation.
Repo cleanup workflow for dead code removal, stale comment cleanup, naming consistency, redundant code reduction, and safe maintainability improvements. USE FOR: requests like "clean up", maintenance passes, removing unused imports or variables, pruning TODOs, and replacing inappropriate production print statements. DO NOT USE FOR: speculative rewrites, major architecture changes, or broad dependency upgrades.
Behavior-preserving refactor workflow for simplifying logic, extracting smaller functions, consolidating duplication, and improving naming and structure. USE FOR: requests like "refactor", "simplify this module", or "break this function down". DO NOT USE FOR: feature work, speculative rewrites, or dependency-management tasks.
Rules and workflow for writing and editing project documentation. USE FOR: creating or updating Markdown files in docs/; checking documentation style; understanding line-length limits; writing headings, code blocks, or links correctly; running markdownlint. DO NOT USE FOR: writing code comments or docstrings; general coding tasks.
How to add Python or Node.js dependencies to this project. USE FOR: adding a new package; understanding where dependencies are declared; knowing what to run after adding a dependency; understanding how security scanning covers new dependencies. DO NOT USE FOR: general coding; writing tests; deployment.
| name | semantic-commits |
| description | Write descriptive conventional commit messages that explain intent. USE FOR: committing changes; reviewing staged diffs; drafting commit messages; when the user asks to commit. DO NOT USE FOR: general coding; writing tests; deployment. |
Every commit in this project uses the Conventional Commits format. Messages must be descriptive — explain why the change was made, not just what changed.
<type>(<scope>): <subject>
[optional body]
[optional footer(s)]
| Type | When to use |
|---|---|
feat | New user-facing feature or capability |
fix | Bug fix |
docs | Documentation only (Markdown, docstrings, comments) |
refactor | Code change that neither fixes a bug nor adds a feature |
test | Adding or updating tests |
ci | CI/CD pipeline or workflow changes |
chore | Maintenance (deps, build scripts, tooling) |
A short noun identifying the area of the codebase. Use the scopes that already appear in the git log when they fit:
translator, organizer, converter, docker, cd, ci, deps, makefile,
security, http, tools, skills
Add a new scope only when none of the above applies.
fix(converter): handle fractional cups in metric conversionfix(converter): change if statementAdd a body for any commit where the subject alone does not explain:
Wrap body lines at 72 characters. Separate from the subject with a blank line.
Append ! after the type/scope and add a BREAKING CHANGE: footer:
feat(translator)!: require API key via environment variable
BREAKING CHANGE: the --api-key CLI flag has been removed;
set OPENAI_API_KEY instead.
When the user asks you to commit:
git diff --cached (and git status) to understand staged changes.git log --oneline -10) to match the project's
existing voice and scope conventions.git commit -m "$(cat <<'EOF'
feat(translator): support DeepL as an alternative backend
Add a --backend flag that accepts "openai" (default) or "deepl".
The DeepL provider reuses the same async HTTP client pool.
EOF
)"
fix(cd): use git ancestry check for prod builds instead of head_branch
feat(http): enable HTTP/2 for improved request performance (#41)
refactor(tools): extract shared model comparison fixtures
docs(skills): expand GitHub deployment skill with release plan (#50)
chore(deps): upgrade to Python 3.14 and Node.js 24 (#43)
test(converter): add comprehensive unit converter tests
ci(deps): bump dorny/test-reporter in the github-actions group (#45)