skills.rest
heykvnzhao
heykvnzhaoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

git-commit-plan

Generate a numbered commit plan with file selections and git commands.

Updated Jan 17, 2026
Search Tags:#git#workflow#commit#staging#plan#version-control#conventional-commits
One-click install
npx skills add https://github.com/heykvnzhao/dotfiles --skill git-commit-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit-plan
Source: https://github.com/heykvnzhao/dotfiles/tree/main/skills/git-commit-plan
Command: npx skills add https://github.com/heykvnzhao/dotfiles --skill git-commit-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan commits from the current working tree to help you split changes into coherent commits, decide what to stage, and craft messages with an execution plan.

Core Features & Use Cases

  • Group changes by intent (feature/fix/refactor/docs/chore) and scope to keep commits focused.
  • Propose Conventional Commit messages and exact files per commit to ensure consistent history.
  • Output a concrete, numbered plan with the specific files to include and notes on grouping, plus recommended git commands (stage/commit) to follow.
  • Ask for explicit confirmation before staging or committing to prevent accidental changes.

Quick Start

Tell me how you want to split the current changes and I will generate a commit plan with the commands to execute.

Frequently Asked Questions about git-commit-plan

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

FAQPage Schema
How do I split my git working tree changes into focused commits?▼

To split your git working tree changes into focused commits, group changes by intent and scope, then generate a concrete, numbered plan with specific file selections and precise staging commands to execute.

What is the best way to generate conventional commit messages for staged files?▼

The best way to generate conventional commit messages is by grouping work-tree changes by feature, fix, or refactor scope, then proposing structured messages for each planned commit step.

How do I plan git staging for untracked files before committing?▼

Plan git staging for untracked files by evaluating your repository state, grouping related untracked changes with tracked modifications by intent, and outputting exact git commands to stage them.

Can I get a numbered commit execution plan with exact git commands?▼

Yes, you can get a numbered commit execution plan with exact git commands by analyzing your current repository state and proposing specific stage and commit instructions for each grouped change set.

Does this commit planning approach ask for confirmation before staging changes?▼

Yes, this commit planning approach asks for explicit confirmation before staging or committing changes to prevent accidental modifications to your repository history.

When should I avoid automated git commit planning?▼

You should avoid automated git commit planning when your working tree changes are entirely unrelated and cannot be grouped into coherent, focused commits by intent or scope.

Related Skills

Explore More Software Engineering Skills→
t-miura-024t-miura-024

mt-check-git-diff

Analyze git repository changes and retrieve detailed diffs for modified files.

Community
Intermediate
0xrafasec0xrafasec
9

commit

Stage and commit git changes with conventional commit messages.

Community
Intermediate
opmauopmau
6

commit

Create conventional commits from staged git changes with confirmation.

Community
Intermediate
wadvancedwadvanced
11

gate-commit

Gate commits on mix consistency and group staged changes into conventional commit messages.

Official
Intermediate