skills.rest
djalmaaraujo
djalmaaraujoCOMMUNITY
Explore all skills by this author →
GitHub

planner-commit

Automate git commits after plan execution with conventional or simple messages.

Updated Jan 12, 2026
Search Tags:#automation#git#bash#commits#version-control#plan-execution#conventional-commits
One-click install
npx skills add https://github.com/djalmaaraujo/claude-code-plugins --skill planner-commit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planner-commit
Source: https://github.com/djalmaaraujo/claude-code-plugins/tree/main/plugins/planner/skills/planner-commit
Command: npx skills add https://github.com/djalmaaraujo/claude-code-plugins --skill planner-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates git commits after plan execution to ensure consistent messaging and traceability across plan runs.

Core Features & Use Cases

  • Supports Conventional Commits styling and a simple default format, deriving the scope from the plan filename.
  • Enforces subject formatting (imperative mood, concise length) and automatically includes a body when multiple files change.
  • Integrates with plan-executor auto_commit to produce staged commits using Bash tooling.

Quick Start

Enable auto_commit and run a plan to automatically generate and apply a commit message.

Frequently Asked Questions about planner-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git commits after a plan execution workflow?▼

Automating git commits after plan execution requires enabling auto_commit in a plan-executor workflow, which stages changes and generates commit messages using Bash tooling. The scope is derived from the plan filename.

What is the conventional commits format for automated commit messages?▼

Conventional commits format structures automated commit messages by deriving the scope from the plan filename, enforcing imperative mood, limiting subject length, and appending a body when multiple files change during execution.

How do I set up auto_commit to use conventional commits styling with bash?▼

To set up auto_commit, enable the feature in your plan-executor workflow and execute the plan. The system uses Bash tooling to stage files and apply commits, deriving the scope from the plan name and formatting the subject accordingly.

Can I use a simple commit format instead of conventional commits for plan automation?▼

Yes, the automation supports both conventional commit style and a simple default format for commit messages. It derives the scope from the plan filename and prescribes git staging and commit commands with optional bodies for both formats.

Does the automated commit tooling enforce subject length and body formatting rules?▼

Yes, the automated commit tooling enforces subject formatting by requiring imperative mood and concise length. It automatically includes a formatted body in the commit message when multiple files change during the plan execution.

Related Skills

Explore More Software Engineering Skills→
jburns24jburns24

commit

Create conventional commits with embedded generation metadata from staged changes.

Community
Intermediate
yaronshereryaronsherer

smart-push

Automate Git commits, pushes, and GitHub Actions CI monitoring with auto-fixes.

Community
Advanced
ThedouglerThedougler

git-commit

Generate conventional git commit messages with automated file staging.

Community
Intermediate
lee-tolee-to
1.1k

ai-factory.commit

Generate conventional commit messages from staged Git changes.

Community
Intermediate