ワンクリックで
commit
// Analyze changes, group into logical units, and create conventional commits with gitmoji. Use when committing code changes.
// Analyze changes, group into logical units, and create conventional commits with gitmoji. Use when committing code changes.
This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step. It applies when a brainstorm or plan document exists and the user wants to improve it.
Use when a workflow command needs to detect multi-service monorepos, prompt for service scope, and propagate `<focus_context>` to sub-agents. Triggers when `--services` is passed, when focus context already exists in the conversation, or when multiple `pyproject.toml` files exist at the repo root.
Configure which review agents run for your project. Auto-detects Python stack and writes compound-engineering.local.md.
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
Implement async task queues with Celery and real-time WebSocket support with Django Channels. Use when a Django project includes celery or channels in its dependencies, or when implementing background processing, periodic tasks, WebSocket connections, or real-time features.
| name | commit |
| description | Analyze changes, group into logical units, and create conventional commits with gitmoji. Use when committing code changes. |
| model | sonnet |
| allowed-tools | Bash, Read, Grep, Glob, AskUserQuestion |
| user-invocable | true |
Analyze all uncommitted changes, group them into logical commit units, and create conventional commits with gitmoji — balancing atomicity with density.
/commit
<type>(<scope>): <emoji> <description>
<optional body>
<emoji> <change description>
<emoji> <change description>
Breaking change: feat(auth)!: 💥 remove legacy token format
Full emoji table (subject + body): references/emoji-table.md.
git status
git diff
git diff --cached
git log --oneline -5
If no changes, report "No changes to commit." and stop.
Priority rules:
Edge cases: single file → one group, no prompt. All related → one commit. Can't decide → ask user.
Present groups and wait for confirmation:
Group 1 → feat(auth): ✨ add login endpoint
- src/auth/views.py (new)
- src/auth/urls.py (modified)
- tests/auth/test_login.py (new)
Group 2 → chore: 🔧 update pre-commit config
- .pre-commit-config.yaml (modified)
Commit group 1 first? [Y/n/edit]
Auto-detect:
src/<app>/<module>/ → scope <module>featfixtestdocsrefactorchorecibuildperfstyleAmbiguous → ask.
Propose --amend only if ALL:
git log --oneline @{u}..HEAD shows it)Ask: "Last commit was feat(auth): ✨ add login endpoint — these changes extend it. Amend? [Y/n]"
When amending, update the body to include new changes.
Show full message + file list. Wait for confirm/edit/skip.
git add <file1> <file2> ...
git commit -m "$(cat <<'EOF'
feat(auth): ✨ add login endpoint
✅ add login view with JWT token generation
🔧 configure auth URLs in router
🧪 add tests for login success and failure
EOF
)"
Amend variant uses git commit --amend -m "$(cat <<'EOF' ... EOF)".
If the hook fails:
NEVER skip hooks with --no-verify.
More groups → back to Step 3. All done → summary:
Done! Created 2 commits:
abc1234 feat(auth): ✨ add login endpoint
def5678 chore: 🔧 update pre-commit config