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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents risky or messy Git commits by analyzing staged changes, blocking sensitive files, enforcing safety rules, and producing clear conventional commit messages with user confirmation.

Core Features & Use Cases

  • Atomic commit planning: Groups staged changes by functionality so each commit represents one logical change.
  • Conventional commit formatting: Generates messages in type(scope): description format with a mandatory attribution line.
  • Sensitive file detection: Blocks commits that include common secret patterns like .env, keys, and credentials files.
  • Guardrails for safe workflows: Enforces non-destructive defaults (no direct main/master commits in project mode, no skipping hooks, no amend/force-push behaviors).
  • User verification gate: Presents a commit plan and requires explicit approval before creating commits.

Quick Start

Use the commit skill to plan and create safe conventional Git commits for your staged changes.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I generate conventional commit messages from staged Git changes?

To generate conventional commit messages, the Skill analyzes your staged Git diffs and outputs type(scope): description formatting with a mandatory attribution line. It groups changes into atomic units and requires explicit user verification before committing.

What is an atomic Git commit and how does it group staged changes?

An atomic Git commit represents one logical change. The Skill achieves this by analyzing staged changes, grouping related files by functionality, and planning separate commits for each distinct concern before requesting user approval.

Can I block sensitive files like .env from being committed in Git?

Yes, you can block sensitive files from Git commits. The Skill enforces safety by detecting common secret patterns like .env, keys, and credentials files, actively preventing them from being included in your commit operations.

Does this commit workflow enforce guardrails against pushing directly to main?

Yes, the commit workflow enforces non-destructive guardrails. In project mode, it blocks direct commits to main or master branches, prevents skipping pre-commit hooks, and disallows amend or force-push behaviors.

How do I split a multi-concern staged diff into separate commits?

To split a multi-concern staged diff, the Skill evaluates the changes and groups them into atomic units based on functionality. It presents a commit plan for your explicit approval, creating separate conventional commits for each logical group.