draft-commit

Drafts atomic commit plans and Conventional Commits messages from scoped Git change sets.

Updated May 12, 2026
One-click install
npx skills add https://github.com/mtk177a/skills --skill draft-commit-mtk177a
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: draft-commit
Source: https://github.com/mtk177a/skills/tree/main/skills/draft-commit
Command: npx skills add https://github.com/mtk177a/skills --skill draft-commit-mtk177a

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing good commit messages and splitting mixed staged, unstaged, and untracked changes into clean atomic commits is error-prone: unrelated work gets absorbed, breaking changes go unmarked, and secrets slip into history. This Skill produces a read-only commit plan and complete Conventional Commits messages without touching the repository. ## Core Features & Use Cases - Atomic Commit Splitting: Groups changes by coherent purpose and dependency, assigns every path or hunk exactly once, and never merges independent concerns to hit a numeric limit. - Conventional Commits Drafting: Selects types from repository conventions and confirmed intent, marks breaking changes with ! or a BREAKING CHANGE: footer, and respects repository or user summary-language rules. - Safety Boundaries: Distinguishes staged, unstaged, untracked, partially staged, and supplied-only diffs; redacts suspected secrets; emits candidate commands only when repository state is verified and paths can be quoted safely. - Use Case: You have a staged fix and an unstaged refactor in the same file. Ask for a staged-only commit plan and receive a fix message covering only the staged hunks, with the unstaged work explicitly excluded and no git add proposed. ## Quick Start Ask the agent to draft an atomic commit plan and Conventional Commits message for your staged changes while keeping all unstaged and untracked work out of the plan.

Frequently Asked Questions about draft-commit

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

FAQPage Schema
How do I split staged and unstaged changes into atomic commits?▼

Provide the change scope and let the Skill build an inventory that assigns every path or hunk exactly once to a commit, an exclusion, or an unresolved state. It groups changes by coherent purpose and dependency without imposing a numeric cap on commit count.

How do I write a Conventional Commits message for my changes?▼

The Skill selects the type from your repository's conventions and confirmed change intent rather than diff syntax, then drafts the full message including scope, body, and footers. Breaking changes are always marked with ! or a BREAKING CHANGE footer.

Does this Skill run git add or git commit for me?▼

No. It is strictly read-only and returns a draft plan and staging handoff. Candidate commands appear only when repository state was verified and paths can be represented safely; invoking the Skill never authorizes staging, committing, or pushing.

Can I draft a commit message from a pasted diff without a repository?▼

Yes. A supplied diff is classified as Provided diff only, which supports semantic message drafting. Because the actual index is unverified, no staging or commit commands are emitted for supplied-only input.

What happens if my diff contains a secret or credential?▼

The suspected value is never reproduced and the affected material is excluded from the normal commit plan. The Skill reports only the minimum path and category needed plus the required remediation or uncertainty.

When should I not use this Skill?▼

Do not use it for PR descriptions, diff reviews, or implementing changes; those belong to summarize, review, or implementation workflows. It only drafts commit units and messages and never writes to the repository.