commit

Plan and execute Git commits from staged changes in dependency order.

30|4|Updated Dec 24, 2025
One-click install
npx skills add https://github.com/oursky/skytest-agent --skill commit-oursky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/oursky/skytest-agent/tree/main/skills/development-skills/commit
Command: npx skills add https://github.com/oursky/skytest-agent --skill commit-oursky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers manage their Git workflow by intelligently planning and creating commits from staged changes, ensuring logical separation and clear commit messages.

Core Features & Use Cases

  • Logical Commit Planning: Automatically groups staged files into sensible, ordered commit units.
  • Commit Message Suggestions: Generates clear, imperative commit titles and allows for optional footers (e.g., refs: #42).
  • Approval-Based Execution: Presents a plan for user review and approval before executing any Git commands.
  • Use Case: When you have multiple related changes staged, use this Skill to split them into atomic commits, making your Git history cleaner and easier to review.

Quick Start

Use the commit skill to plan commits for the staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I split staged Git changes into logical commits?

You can split staged changes into atomic commits by using this Skill to group staged files into ordered units, generate imperative commit titles, and execute commits in dependency order.

Can I generate Git commit messages from staged files automatically?

Yes, you can generate Git commit messages from staged files automatically. This Skill analyzes staged changes to suggest clear, imperative commit titles and optional footers like issue references.

Does this Git workflow tool commit changes without user approval?

No, this Git workflow tool requires explicit user approval. It presents a commit plan for review and strictly operates on staged files, executing Git commands only after you approve the plan.

What is the best way to organize multiple staged files into atomic Git commits?

The best way to organize multiple staged files into atomic Git commits is intelligently planning logical separation. This Skill groups staged files into sensible, ordered units to keep your project history clean.

How do I add issue tracking footers to my Git commit messages?

To add issue tracking footers to Git commit messages, this Skill allows you to append optional footers, such as issue references, when generating the commit plan for your staged changes.

Why should I use a planning tool for version control instead of committing everything at once?

Using a planning tool for version control ensures logical separation of changes. This Skill splits staged files into atomic commits, making your Git history cleaner and significantly easier to review.