Menu
Create a well-formatted commit following project conventions. Auto-detects commit style from git history.
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
Comprehensive business research for market analysis, competitor intelligence, trend detection, and idea validation. Triggers on research requests, market sizing questions, competitor analysis needs, idea validation, TAM/SAM/SOM calculations, SWOT analysis, and timing assessments. Use when building business cases, evaluating opportunities, or validating product ideas.
Plan execution methodology and verification strategies. Triggers on: "execute plan", "implement plan", "run plan", "follow the plan", "start implementation", "continue execution", "resume plan". Provides execution patterns, progress tracking, and error handling strategies.
Implementation planning methodology and patterns. Triggers on: "plan", "design", "architect", "structure", "how should I implement", "before I start coding", "implementation plan", "feature planning", "break down this feature". Provides planning patterns, templates, and analysis strategies.
Test-Driven Development methodology and patterns. Triggers on: "tdd", "test first", "write tests", "failing test", "red green refactor", "test driven", "test before", "coverage", "unit test", "feature test", "widget test". Provides TDD patterns for Laravel (PHPUnit/Pest), Flutter, and Vue (Vitest/Jest).
Review uncommitted code changes for bugs, security vulnerabilities, and quality issues. Use before commits or when asked to review code.
Update inline documentation for uncommitted code changes. Use after modifying code or when documentation needs sync.
| name | commit-changes |
| description | Create a well-formatted commit following project conventions. Auto-detects commit style from git history. |
Create a commit for staged/unstaged changes following project conventions.
git status for changesgit log --oneline -10 to detect commit styleUse the detection script for accurate results:
# Returns JSON with style and confidence
"${CLAUDE_PLUGIN_ROOT}/scripts/detect-commit-style.sh"
Output example:
{
"style": "conventional-scoped",
"confidence": 80,
"stats": { "total": 10, "conventional_scoped": 8, "gitmoji": 2 }
}
| Pattern | Style |
|---|---|
type(scope): message | Conventional Commits (scoped) |
type: message | Conventional (no scope) |
:emoji: message | Gitmoji |
| Plain text | Simple |
| Type | Use For |
|---|---|
| feat | New features |
| fix | Bug fixes |
| docs | Documentation only |
| style | Formatting changes |
| refactor | Code restructuring |
| perf | Performance improvements |
| test | Adding/fixing tests |
| chore | Maintenance tasks |
<type>(<scope>): <subject>
<body>
<footer>
Subject Rules:
Body (optional):
Footer (optional):
Closes #123BREAKING CHANGE: descriptionPresent message for approval before committing.