git-commit

Stage and commit changed files as atomic Conventional Commits with branch-safety checks.

121|10|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sortie-ai/sortie --skill git-commit-sortie-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/sortie-ai/sortie/tree/main/.github/skills/git-commit
Command: npx skills add https://github.com/sortie-ai/sortie --skill git-commit-sortie-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when you need to commit, save, or persist changes to Git. It ensures atomic commits, branch safety, Conventional Commits formatting, and aligns with project style guidelines. Do NOT use for pushing, creating PRs, or branch management beyond safety checks.

Core Features & Use Cases

  • Atomic commits: split changes into logical commits to preserve a clear history.
  • Branch safety and style: checks against protected branches and ensures consistent messaging.
  • Conventional Commit compliance: enforces standard commit messages matching project conventions.
  • Workflow guidance: provides steps for safe commits in collaborative environments.

Quick Start

Instruct the AI to stage changes and create an atomic, conventional-commit message for the staged changes.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I create atomic git commits that follow conventional commits?

Atomic git commits are created by identifying logical changes, staging them separately, and writing conventional commit messages. This workflow preserves a clear history by ensuring each commit represents a single, coherent modification.

How do I ensure git branch safety and avoid committing to protected branches?

Git branch safety is enforced by checking the current branch against protected branches before staging changes. This prevents accidental commits to critical branches and ensures collaborative environments maintain version-control integrity.

What is the best way to align commit messages with project style guidelines?

Aligning commit messages with project style guidelines involves applying Conventional Commits formatting to standardize the history. This enforces consistent messaging by structuring commit types and scopes according to project conventions.

Can I use this workflow to push changes and create pull requests?

No, this workflow is strictly for creating atomic commits and does not support pushing changes or creating pull requests. It focuses entirely on local version-control safety, staging, and message hygiene.

Why split changes into logical commits during version control?

Splitting changes into logical commits preserves a clear and navigable project history. By creating atomic commits, you ensure that each entry represents a single purpose, improving traceability and collaborative workflow.