commit

Analyze diffs, stage related changes, and enforce conventional commit messages.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill commit-sqve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/sQVe/cape/tree/main/skills/commit
Command: npx skills add https://github.com/sQVe/cape --skill commit-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates atomic, well-documented commits by guiding selective staging and enforcing conventional commit messages, ensuring a clean, traceable history.

Core Features & Use Cases

  • Staged, atomic commits that group related changes into meaningful units.
  • Enforced conventional commit messages with clear subject and optional scope.
  • Safety guards including per-change commits, pre-commit checks, and required user approval.

Quick Start

Review the diff, stage the relevant files, and commit with a conventional message after user approval.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I create atomic git commits for multiple file changes?

To create atomic git commits, this Skill analyzes your diff and suggests logical commit groups, selectively staging related changes into meaningful units before committing them individually.

What is the best way to enforce conventional commit messages in my workflow?

Enforcing conventional commit messages is handled by the Skill through automated checks that require a clear subject and optional scope, ensuring a clean, traceable project history.

Can I automate selective staging without pausing for user approval?

Yes, you can automate selective staging and bypass interactive approval by using the optional no-confirm mode, allowing the workflow to proceed automatically across multi-file changes.

How does this workflow handle pre-commit hook checks?

The workflow enforces pre-commit hook checks during the staging process, pausing to require explicit user confirmation before finalizing any per-group commit to ensure code quality.

Why should I split multi-file changes into per-group commits?

Splitting multi-file changes into per-group commits isolates logical changes, preventing unrelated modifications from mixing and maintaining a clean, traceable history for easier debugging.