Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From planner
Handle git commits for plan execution with support for Conventional Commits or simple format. Called by plan-executor when auto_commit is enabled.
How this skill is triggered — by the user, by Claude, or both
Slash command
/planner:skills/planner-commitThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill handles git commits after successful plan execution, respecting the configured commit message standard.
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 committingnpx claudepluginhub djalmaaraujo/claude-code-plugins --plugin plannerCreates conventional commit messages for staged git changes following the Conventional Commits spec and VGV workflow. Stages unstaged files interactively when needed.
Manages git commit workflows: checks status and diffs, stages changes selectively, generates and validates conventional commit messages, then executes commits.
Analyzes staged Git changes, generates a Conventional Commits format message, and executes the commit. Useful for automating commit message formatting and ensuring consistency.