commit-plan

Plan and execute Git commits by intent with approval steps.

64|2|Updated Feb 8, 2018
One-click install
npx skills add https://github.com/yuki-yano/dotfiles --skill commit-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-plan
Source: https://github.com/yuki-yano/dotfiles/tree/main/.agents/skills/commit-plan
Command: npx skills add https://github.com/yuki-yano/dotfiles --skill commit-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates the organization of Git changes by intent, creating a staged, reviewable commit plan before applying changes.

Core Features & Use Cases

  • Intent-based commit planning: groups changes into logical commits for easier review.
  • Phase-based execution: separates planning and execution with a one-character approval step.
  • Safety and recoverability: provides backup and safe patch application with guardrails for rollback.
  • Targeted scope: supports file-path and type filters to limit the plan to specific changes.

Quick Start

Summarize the requested changes by intent and present an approval-ready, phase-by-phase commit plan.

Frequently Asked Questions about commit-plan

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

FAQPage Schema
How do I plan git commits by intent before applying changes?

Phase-based git execution separates planning and applying changes, requiring a one-character approval step before proceeding to ensure safe patch application and providing guardrails for rollback.

Can I target specific file paths when planning a git commit workflow?

Yes, you can target specific file paths and type filters to limit the commit plan, ensuring the phase-based execution only includes the scoped repository changes you intend to modify.

How do I safely execute a multi-step git commit sequence?

You safely execute a multi-step git commit sequence by using a phase-based approach that implements strict safety checks, backups, and a one-character approval step between planning and applying changes.

What is the best way to group version-controlled changes into logical commits?

The best way to group version-controlled changes into logical commits is intent-based planning, which organizes code edits and documentation updates into a staged, reviewable sequence before execution.

Does this commit planning approach support recoverability for failed git patches?

Yes, the approach supports recoverability by providing backups and safe patch application with guardrails, allowing you to rollback repository changes if a planned execution phase fails.