メニュー
Generates Conventional Commit messages from a git diff and can propose commit splitting or a short PR summary. Use when deriving a semantic commit from staged or unstaged changes. Don't use for bugfix, refactor, or review execution.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | semantic-commit |
| description | Generates Conventional Commit messages from a git diff and can propose commit splitting or a short PR summary. Use when deriving a semantic commit from staged or unstaged changes. Don't use for bugfix, refactor, or review execution. |
Inferir tipo de commit a partir de evidência do diff Usar formato Conventional Commit
<type>(scope-opcional): <descrição>
feat, fix, refactor, perf, docs, test, chore, build, ci, style
assets/output-template.md antes de montar a resposta final.feat > fix > refactor > perf > docs > test > chore > build > ci > style.done: commit semântico (e opcionalmente divisão/resumo) gerado a partir do diff.needs_input: diff ausente ou ilegível.scope em vez de inventá-lo.style ou chore conforme a evidência do diff.needs_input.assets/output-template.md.Crafts or improves README files with audience-aware structure, project-type templates, and review guidance. Use when creating, updating, extending, or auditing a README. Don't use for general prose editing that is unrelated to README structure or project documentation.
Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.
Executes root-cause bug fixes with regression tests and validation evidence. Use when fixing documented defects or reviewer findings. Don't use for code review-only tasks or refactor-only requests.
Performs safe, incremental refactors that preserve behavior and reduce complexity. Use when simplifying code, isolating hotspots, or improving maintainability. Don't use for bugfix-only requests or review-only audits.
Reviews code and functional changes against rules, requirements, and objective evidence. Use when auditing a diff, validating a task, or issuing an approval gate. Don't use for implementing fixes without a review scope.