Menu
Commit message format standards using Conventional Commits specification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Always use Turborepo commands for building, testing, and serving projects in this monorepo
Always use Turborepo commands for building, testing, and serving projects in this monorepo
Complete guide for Mastra development — agents, tools, workflows, vertical organization, and type safety
Always fix issues you encounter, even if unrelated to your current task
Essential clean code practices including naming, comments, and structure
Use GitHub MCP tools for all repository operations instead of CLI or API calls
| name | conventional-commits |
| description | Commit message format standards using Conventional Commits specification |
CRITICAL: ALWAYS follow Conventional Commits format
<type>(<scope>): <subject>
<body>
<footer>
Use project-specific scopes:
Root level:
deps, config, ci, buildMCP project:
mcp, agents, workflows, toolsweather, shopping, cooking, codingOther projects:
firmware, elevenlabsfeat(mcp): add calendar agent for scheduling
fix(shopping): correct product quantity calculation
docs(agents): update workflow examples
feat(api)!: change authentication method
BREAKING CHANGE: Auth now requires API key
Closes #123Add ! before colon for breaking changes:
feat(api)!: change authentication method
BREAKING CHANGE: Auth now requires API key instead of username/password
PR titles must also follow Conventional Commits format:
feat(mcp): add calendar agent for scheduling
fix(shopping): correct product quantity calculation
❌ Don't use vague subjects like "fix bug" or "update code" ❌ Don't capitalize subject line ❌ Don't end subject with period ❌ Don't mix multiple types in one commit ❌ Don't forget scope when applicable ❌ Don't exceed 72 characters in subject