Conventional commit message format with ticket extraction from branch names
Format: <type>(<scope>): <subject>
type: feat | fix | docs | style | refactor | test | chore
scope: Ticket ID from branch (e.g., BROCARD-123) or branch name if no ticket
subject: Present tense, no period, <72 chars
Never include author names - Git tracks authorship automatically
Extract PROJECTNAME-NUMBER from branch name:
feature/MYPROJECT-985 → MYPROJECT-985bugfix/MYPROJECT-123-fix-login → MYPROJECT-123If no ticket pattern found, use full branch name:
main → mainhotfix → hotfixfeat(MYPROJECT-985): add total count to recently viewed products
fix(MYPROJECT-123): resolve login timeout issue
refactor(main): rename user service methods
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