メニュー
Prompt and workflow for generating conventional commit messages. Use when: - Committing changes with standardized messages - Following the Conventional Commits specification - Generating commit messages from staged changes
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | conventional-commit |
| description | Prompt and workflow for generating conventional commit messages. Use when: - Committing changes with standardized messages - Following the Conventional Commits specification - Generating commit messages from staged changes |
git status to review changed filesgit diff or git diff --cached to inspect changesgit add <file>git commit -m "type(scope): description"type(scope): description
[optional body]
[optional footer]
| Type | Use For |
|---|---|
feat | New feature |
fix | Bug fix |
docs | Documentation only |
style | Formatting, no code change |
refactor | Code change that neither fixes nor adds |
perf | Performance improvement |
test | Adding or updating tests |
build | Build system or dependencies |
ci | CI configuration |
chore | Maintenance tasks |
revert | Reverting a previous commit |
Optional but recommended. Use the service or module name:
agent, functions, web-app, infra, docs, scriptsfeat(agent): add memory compaction for long conversations
fix(functions): handle empty HTML in fn-convert
docs(epics): mark story 3 complete in epic 011
refactor(web-app): extract sidebar component
ci: add pre-commit hook for linting
chore: update uv lockfile
feat!: migrate to Responses API (BREAKING CHANGE: old chat endpoint removed)
BREAKING CHANGE: ...) or issue references (Closes #123)Structured first-pass debugging for test failures, runtime errors, and unexpected behavior. USE FOR: test failure, assertion error, ImportError, traceback, debug failing test, fix broken test, diagnose error, runtime exception, mock error, config error. DO NOT USE FOR: complex multi-system design issues (escalate to @planner for re-planning).
Create, update, refactor, explain, or review Microsoft Agent Framework solutions. Use when working with the KB Agent (src/agent/) or any Microsoft Agent Framework code.
Patterns for adding governance, safety, and trust controls to AI agent systems using Microsoft Foundry and Azure API Management (APIM) AI Gateway. Use when: - Adding rate limiting, content safety, or jailbreak detection to agent traffic - Configuring APIM policies for token limits, throttling, or semantic caching - Leveraging Foundry tracing, evaluations, and agent monitoring - Implementing department-scoped access via JWT claims - Deciding what to handle at the platform layer vs. thin application code
Validates service boundary compliance in the KB Agent project. Use when working on cross-service imports, restructuring modules, or reviewing code that crosses service boundaries.
Performs comprehensive preflight validation of Bicep deployments to Azure. Use when: - Before deploying infrastructure to Azure - Reviewing or preparing Bicep files - Previewing what changes a deployment will make (what-if) - Verifying permissions are sufficient for deployment - Before running `azd -C infra/azure up`, `azd -C infra/azure provision`, or `az deployment` commands
Reviews Bicep modules, azure.yaml, and infrastructure changes for the KB Agent project. Checks naming, RBAC, module wiring, and doc sync. Use when working on infra/ or reviewing infrastructure PRs.