git-commit

Generates Conventional Commits messages from staged diffs and commits after user approval.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/epicodic/drift --skill git-commit-epicodic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/epicodic/drift/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/epicodic/drift --skill git-commit-epicodic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, well-structured commit messages is tedious and often skipped, leading to unreadable git history. This Skill inspects your staged changes, drafts a Conventional Commits message, and commits only after you approve it. ## Core Features & Use Cases - Diff-Based Message Drafting: Reads git diff --cached to derive an accurate subject and body describing what actually changed. - Conventional Commits Formatting: Enforces type prefixes (feat, fix, refactor, docs, test, chore, move), optional scopes, 72-character limits, and imperative mood. - Mandatory Confirmation Flow: Presents the proposed message with Approve, Edit in chat, Edit in editor, or Cancel options before any commit runs. - Use Case: After staging a refactoring across several modules, ask for a commit and receive a message like refactor(core): extract layout engine into standalone module with a bulleted body, ready to approve or edit. ## Quick Start Ask the assistant to commit my staged changes with a proper commit message.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I write a Conventional Commits message automatically?▼

Stage your changes with git add, then invoke this Skill. It reads the staged diff, drafts a message with the correct type prefix and scope, and asks for your approval before running git commit.

How to commit staged changes with a generated message?▼

The Skill runs git diff --cached to summarize staged files, derives a subject and optional bulleted body, presents it for confirmation, and executes git commit -m with the approved text.

What happens if nothing is staged in git?▼

The Skill checks the staged diff first. If git diff --cached returns nothing, it notifies you that no changes are staged and stops without attempting a commit.

Can I edit the commit message before committing?▼

Yes. The confirmation step offers Edit in chat or Edit in editor options. Edited messages are shown again for approval, and no commit runs until you explicitly select Approve.

Does the commit skip git hooks like pre-commit?▼

No. The Skill runs a standard git commit and does not pass --no-verify unless you explicitly request it, so configured hooks such as pre-commit and commit-msg still execute.