Handle git commits for plan execution with support for Conventional Commits or simple format. Called by plan-executor when auto_commit is enabled.
Creates git commits for plan execution using Conventional Commits or simple format.
/plugin marketplace add djalmaaraujo/claude-code-plugins/plugin install planner@djalmaaraujo-claude-code-pluginsThis skill is limited to using the following tools:
This skill handles git commits after successful plan execution, respecting the configured commit message standard.
When called, you receive:
plan_name: The name of the executed plan (e.g., "auth-01-setup.md")summary: Brief description of what was accomplishedfiles_modified: List of files that were changedauto_commit_standard: Either "conventional_commits" or "no_standard"auto_commit_standard is "conventional_commits"Follow the Conventional Commits specification (v1.0.0):
Format: <type>(<scope>): <description>
Determine the commit type by analyzing the changes:
| Type | When to Use |
|---|---|
feat | New feature or functionality |
fix | Bug fix |
refactor | Code restructuring without behavior change |
docs | Documentation only changes |
test | Adding or updating tests |
chore | Maintenance, dependencies, tooling, config |
style | Formatting, whitespace, missing semicolons (no logic change) |
perf | Performance improvements |
Determine the scope from the plan name:
auth-01-setup.md → scope is authuser-profile-03-api.md → scope is user-profileplanner as the default scopeWrite the description:
Include a body if more than 3 files were modified:
Example commits:
feat(auth): add user authentication endpoints
- Implement login and logout routes
- Add JWT token generation
- Create auth middleware
fix(user-profile): correct avatar upload validation
refactor(planner): reorganize plan execution flow
auto_commit_standard is "no_standard" (or missing)Use the simple format:
feat(planner): Complete [plan_name] - [summary]
Examples:
feat(planner): Complete auth-01-setup.md - Set up authentication module
feat(planner): Complete user-profile-02-api.md - Add profile API endpoints
Stage all modified files:
git add .
Create the commit with the appropriate message format:
git commit -m "<message>"
For multi-line messages (Conventional Commits with body):
git commit -m "<subject>" -m "<body>"
Do NOT push - leave that to the user
git add . before committingThis skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.