メニュー
Write concise Conventional Commit messages that match the actual scope of the change.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | commit |
| description | Write concise Conventional Commit messages that match the actual scope of the change. |
Before committing, tighten the change scope and use Conventional Commit style:
feat(scope): ... for visible capability additionsfix(scope): ... for bug fixesrefactor(scope): ... for behavior-preserving refactorstest(scope): ... for adding or improving testsDo not hide unrelated changes behind one commit message. Write the title around the outcome, not the process.
Create or update a branch-scoped Coolify review environment with one command, and delete it with one command. Use when a ticket must deploy a preview before human review, while keeping the workflow simple and fast.
Write workflow harness files that define role, status semantics, feedback loops, and durable delivery rules for disposable ticket workspaces.
Clarify ambiguous requests with a focused, Socratic interview before planning or implementation.
Review behavior, risk, performance, and test coverage before style nits.
Review trust boundaries, auth, input handling, secrets, and dependency risk before release.
Turn a clarified spec into milestone-oriented tickets, dependency edges, and stage-gated delivery lanes.