commit

Stage and commit working tree changes as logically grouped commits.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/yannickloth/health-me-cfs --skill commit-yannickloth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/yannickloth/health-me-cfs/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/yannickloth/health-me-cfs --skill commit-yannickloth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stage and commit working tree changes as logically grouped commits.

Core Features & Use Cases

  • Atomic commits: each commit represents a single logical change.
  • Noise reduction: filters out temporary files, build artifacts, and generated files.
  • Scoped commits: enforces grouping by logical scope and consistent messaging.

Quick Start

Instruct the system to stage changes as cohesive commits and apply conventional commit messages.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I group git changes into atomic commits automatically?

To group git changes into atomic commits, this skill stages working tree changes as logically grouped units. It scopes changes to meaningful units and filters out noise like temporary files for a clean version-control history.

What is the best way to apply conventional commit messages to staged changes?

The best way to apply conventional commit messages is by instructing the system to stage changes as cohesive commits. This skill enforces deterministic grouping and messaging adherence for meaningful version-control commits.

How do I filter out build artifacts and temporary files before committing?

To filter out build artifacts and temporary files before committing, this skill performs noise reduction during the staging process. It ensures only meaningful logical changes are included in your version-control history.

Does automatic git commit grouping work without manual staging?

Yes, automatic git commit grouping works without manual staging by scoping working tree changes directly. It enforces grouping by logical scope and applies consistent conventional-commit messaging automatically.

Can I enforce consistent messaging across multiple scoped commits?

Yes, you can enforce consistent messaging across multiple scoped commits. This skill enforces grouping by logical scope and adheres to conventional-commit style, ensuring deterministic messaging for every logical change.