One-click install
npx skills add https://github.com/mmahalwy/cooper --skill git-commit-mmahalwy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/mmahalwy/cooper/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/mmahalwy/cooper --skill git-commit-mmahalwy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually crafting conventional commit messages and deciding what to stage can be time consuming and inconsistent, leading to unclear git history and poor traceability. This Skill automates message generation and staging decisions by analyzing diffs and applying Conventional Commits conventions so commits are consistent, descriptive, and safe.

Core Features & Use Cases

  • Diff analysis for intent: Inspect staged or working-tree diffs to infer whether changes are features, fixes, docs, tests, refactors, or other types.
  • Scope detection and concise descriptions: Propose an appropriate optional scope and a present-tense, imperative one-line description that fits conventional commit guidelines.
  • Intelligent staging and interactive flow: Recommend or perform targeted staging of files and support interactive overrides for type, scope, and description before committing.
  • Safe execution and best practices: Execute non-destructive git commit commands, avoid forceful or risky operations, and follow rules for not committing secrets and not bypassing hooks.
  • Use Case: When finishing a bug fix across multiple files, use the Skill to group related files, generate a fix scope and description, and create a clean conventional commit.

Quick Start

Commit current changes with an auto-generated conventional commit message and interactively adjust type, scope, or description if needed.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages from a git diff automatically?

To generate conventional commits from a git diff, this Skill analyzes your staged or unstaged changes to infer the type and scope, then proposes a concise, present-tense imperative description for your commit.

What is the best way to group changed files for a single conventional commit?

The best way to group changed files for a conventional commit is using intelligent staging, which analyzes your working-tree diff to recommend targeted file staging and group related changes together before committing.

Can I override the generated commit type and scope before executing the git commit?

Yes, you can override the generated commit type and scope before executing the git commit. The Skill supports an interactive flow allowing you to adjust the type, scope, and description prior to finalizing the operation.

Does this automated git commit process bypass git hooks or force updates?

No, this automated git commit process does not bypass git hooks or force updates. It executes non-destructive git commit commands, explicitly avoiding forceful or risky operations while enforcing rules against committing secrets.

Why should I use an automated tool for conventional commits instead of writing them manually?

You should use an automated tool for conventional commits because manually crafting messages and deciding what to stage is time-consuming and inconsistent, leading to unclear git history and poor traceability across your project.