Generate conventional commit messages for the current git changes and optionally perform the commit. Use when asked to draft a commit message, prepare a commit, or summarize staged/working-tree changes into a conventional commit format with scope inferred from branch naming.
Generate a conventional commit message by inspecting current git changes, extracting a scope from the branch name, and presenting clear next-step options to the user.
Run these commands and summarize what changed:
git status --short
git branch --show-current
git diff --stat
Call out key files and their purpose (feature, fix, refactor, docs, tests, build, chore).
Extract scope from the branch name using pattern PROJECTNAME-123 (case sensitive). If missing, use the full branch name as the scope.
Choose the conventional commit type based on the changes:
feat: new feature or significant behavior changefix: bug fixrefactor: restructuring without behavior changedocs: documentation onlytest: test-only changesbuild: build system or dependencieschore: maintenance or misc changesIf a commit-style skill is available in the environment, follow its exact formatting rules.
Format the message as:
<type>(<scope>): <short summary>
Keep the summary concise and aligned with the primary change. If multiple changes are present, bias toward the most impactful one and keep the rest for the body only if asked.
Offer the following user choices:
git commit -m "<message>")/commit-plan or provide a multi-commit outline)Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and advanced queries.
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
Start voice calls via the OpenClaw voice-call plugin.
Notion API for creating and managing pages, databases, and blocks.
Gemini CLI for one-shot Q&A, summaries, and generation.
Category:developer