メニュー
Generate intelligent, conventional commit messages based on staged changes. Analyzes diffs, categorizes changes, and creates meaningful commit messages. Use when ready to commit changes and want high-quality commit history.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | git-commit |
| description | Generate intelligent, conventional commit messages based on staged changes. Analyzes diffs, categorizes changes, and creates meaningful commit messages. Use when ready to commit changes and want high-quality commit history. |
Generate meaningful, conventional commit messages by analyzing staged changes. Creates commits that tell a story and make git history useful.
# Check if in a git repo
git rev-parse --git-dir 2>/dev/null || echo "NOT_A_GIT_REPO"
# Check staged changes
git diff --cached --stat
# Check unstaged changes
git status --short
# Get detailed diff of staged changes
git diff --cached
# Get list of files changed
git diff --cached --name-only
# Get change statistics
git diff --cached --shortstat
Determine the commit type based on changes:
| Type | Description | Examples |
|---|---|---|
feat | New feature | New endpoint, new component, new capability |
fix | Bug fix | Error handling, logic correction |
docs | Documentation | README, comments, JSDoc |
style | Formatting | Whitespace, semicolons, no logic change |
refactor | Code restructuring | Rename, extract function, no behavior change |
perf | Performance | Optimization, caching |
test | Tests | New tests, test fixes |
chore | Maintenance | Dependencies, build config |
ci | CI/CD | GitHub Actions, deployment |
Look at changed files to determine scope:
<type>(<scope>): <subject>
<body>
<footer>
Closes #123BREAKING CHANGE: description# Commit with generated message
git commit -m "<type>(<scope>): <subject>" -m "<body>"
# Or if user wants to edit
git commit -e -m "<generated message>"
# Staged: src/components/Button.tsx (new file)
git commit -m "feat(button): add reusable Button component"
# Staged: src/api/auth.ts (modified)
git commit -m "fix(auth): handle expired refresh tokens
Previously, expired refresh tokens caused a 500 error.
Now properly returns 401 and clears the session.
Closes #456"
# Staged: src/api/users.ts, src/types/user.ts, tests/users.test.ts
git commit -m "feat(users): add user profile endpoint
- Add GET /api/users/:id endpoint
- Add User type definitions
- Add integration tests
Closes #789"
git commit -m "refactor(api)!: change response format to JSON:API
BREAKING CHANGE: All API responses now follow JSON:API spec.
Clients must update to handle the new response structure.
Migration guide: docs/migration-v2.md"
If changes are complex, ask user:
I see changes to multiple areas:
- 3 files in src/components/ (UI changes)
- 2 files in src/api/ (backend changes)
- 1 file in tests/ (test updates)
Would you like to:
1. Create a single commit for all changes
2. Split into multiple focused commits
3. Let me suggest a commit message and you review
[1/2/3]?
After committing:
# Show the commit
git log -1 --pretty=format:"%h %s%n%n%b"
# Verify it's pushed (if applicable)
git status
📝 Commit Message Generated
Type: feat
Scope: authentication
Subject: add OAuth2 login flow
Body:
Implement OAuth2 authorization code flow with PKCE.
Supports Google and GitHub providers.
Footer:
Closes #123
---
Execute commit? [Y/n/edit]
Perform thorough code review and audit of implemented features. Compares implementation against the technical plan, checks for AI-specific risks, and provides actionable feedback. Activate for: review, audit, code quality assessment, security review.
Initialize Conductor workflow in a project. Bundles all necessary templates for product context, tech stack, workflow, and tracks. v1.0: Hooks handle phase enforcement - setup focuses on file creation.
Persistence mode instructions for autonomous task completion. Activated when the user includes "ralph", "persistent", or "don't give up" in their prompt. Provides structured guidance for working through tasks systematically.
Structured research methodology for finding documentation, investigating APIs, and synthesizing technical information. Guides systematic research with source verification and organized output. Activate for: research, documentation lookup, investigate, explore concepts.
Plan and design a detailed, phased technical implementation from a PRD. Creates actionable task lists with guardrails for resource efficiency, error handling, and type safety. Activate for: plan, design, technical planning, task breakdown.
Generate documentation for implemented features. The actual code is always the source of truth - document what was built, not what was planned. Creates code comments, README updates, and developer guides as appropriate.