skills.rest
outcomeeng
outcomeengOFFICIAL
Explore all skills by this author →
WebsiteGitHub

committing-changes

Enforce Conventional Commits format with selective staging for atomic git commits.

1|Updated Jan 6, 2026
Search Tags:#git#workflow#commit#code-review#atomic-commits#conventional-commits#selective-staging
One-click install
npx skills add https://github.com/outcomeeng/claude --skill committing-changes-outcomeeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: committing-changes
Source: https://github.com/outcomeeng/claude/tree/main/plugins/core/skills/committing-changes
Command: npx skills add https://github.com/outcomeeng/claude --skill committing-changes-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing consistent, high-quality git commit messages is time-consuming and error-prone; this skill enforces Conventional Commits, ensures selective staging, and maintains atomic commits.

Core Features & Use Cases

  • Enforces Conventional Commits format with type, optional scope, and imperative description.
  • Guides selective staging to avoid accidental full-tree commits.
  • Supports multi-commit workflows: one commit per concern, with splitting rules and review workflow integration.
  • Provides a safe, documented workflow for reviewing changes and ensuring tests pass before commit.

Quick Start

Validate changes with project tooling and then stage files selectively before composing atomic, conventional commits.

Frequently Asked Questions about committing-changes

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

FAQPage Schema
How do I enforce conventional commits format in my git workflow?▼

Conventional commits automation enforces required types, optional scopes, and imperative descriptions, ensuring consistent git histories and atomic commits.

What is the best way to create atomic git commits during code review?▼

Atomic git commits are achieved by guiding selective staging and splitting rules, ensuring one commit per concern to simplify code review workflows.

How do I avoid accidental full-tree commits when staging changes?▼

Avoiding accidental full-tree commits requires selective staging to guide staging specific files, preventing unintended content from entering atomic commits.

Does this conventional commits workflow integrate with pre-commit hooks?▼

Yes, the conventional commits workflow integrates with pre-commit hooks, validating changes and ensuring tests pass before composing atomic commits.

Can I split changes into multiple commits for different modules?▼

Yes, multi-commit workflows are supported with splitting rules, enabling one commit per concern across different modules while maintaining conventional commit standards.

Related Skills

Explore More Software Engineering Skills→
stevengonsalvezstevengonsalvez

commit

Plan, stage, and compose atomic git commits with conventional formatting.

Community
Advanced
barrydobsonbarrydobson

github-actions

Automate secure CI/CD pipelines with GitHub Actions workflows.

Community
Intermediate
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
paulnsorensenpaulnsorensen
2

commit

Stage specific files and create conventional commits in Git.

Community
Intermediate