メニュー
Git commit with Conventional Commits format. Use when user asks to commit changes, says "commit", "/commit", or after completing code changes when explicitly asked to commit.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Author or update tool-neutral knowledge packs in ai-knowledge-base.
A workflow for authoring Go tests. Starting from the table-driven test scaffold generated by gotests, it runs the cycle of test design -> adding test cases -> running -> fixing defects. Use when: (1) invoked via /go-test-authoring, (2) asked to "write tests" or "add tests" for Go, (3) asked to implement tests for a Go function or method.
Create GitHub Pull Request with project's PR template. Use when user asks to create PR, says "create PR", "/pr-create", or after completing implementation when asked to open a pull request.
Address PR review feedback. Collect both unresolved inline comments and review-body comments on a GitHub PR, build a fix plan and turn it into tasks, then work through them one by one (assess -> fix -> commit -> push -> reply). Use when invoked as /pr-review-fix, when asked to "address the review comments" or "respond to PR feedback", or for follow-up work after a PR review.
Internal Structure-Behavior Design skill for conceptual modeling and structure design. Use only as part of the Structure-Behavior Design workflow.
Internal Structure-Behavior Design skill for interface, signature, and contract design. Use only as part of the Structure-Behavior Design workflow.
| id | git-pr-workflow.skill.git-commit |
| kind | skill |
| name | git-commit |
| description | Git commit with Conventional Commits format. Use when user asks to commit changes, says "commit", "/commit", or after completing code changes when explicitly asked to commit. |
| tags | ["git-pr-workflow","git","commit"] |
Create commits following Conventional Commits format with project-appropriate scope.
git status and git diff to understand changesgit log --oneline -10 to learn the project's commit style, scope granularity, and languagegit add<type>(<scope>): <summary>
<body with bullet points>
Co-Authored-By: Claude <noreply@anthropic.com>
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Formatting, no code changerefactor: Code change without feature/fixtest: Adding/updating testschore: Build, CI, dependenciesDetermine from project's commit history:
api, web, auth-service)auth, parser, ui)Write summary in natural language, then list specific changes:
feat(contract): Add subscription cancellation endpoint
Add endpoint to cancel active subscriptions with proration.
- Add CancelSubscription RPC to contract.proto
- Implement cancellation logic in usecase layer
- Add proration calculation for partial periods
Co-Authored-By: Claude <noreply@anthropic.com>
Write the summary and body in the repository's standard language, inferred from recent git log. Keep the Conventional Commits type keyword (feat, fix, ...) in English regardless of the repository language.
git status and git diff first--amend unless explicitly requested--force push--no-verify) unless explicitly requestedgit commit -m "$(cat <<'EOF'
feat(scope): Summary
Body with details.
- Change 1
- Change 2
Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"