commit

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

Updated Apr 10, 2026

Search Tags:#git #commits #best-practices #workflows #code-review #version-control

Ready to run

npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill commit-stevengonsalvez

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/stevengonsalvez/nanoclaw-standalone/tree/main/container/skills/commit
Command: npx skills add https://github.com/stevengonsalvez/nanoclaw-standalone --skill commit-stevengonsalvez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Help developers create well-formatted, meaningful git commits for changes made during a session.

Core Features & Use Cases

Atomic commits: Each commit should address a single purpose.
Structured messages: Follow conventional commit style with a concise subject and detailed body.
Pre-commit cleanup guidance: Ensure environment and temporary files are ignored and the working directory is clean.

Quick Start

Review your session changes and craft a clean, atomic git commit message for each logical change.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I write conventional commit messages for staged git changes?▼

To write conventional commit messages for git changes, structure a concise subject line and detailed body for code review. This enforces conventional commit formatting, selective staging, and atomic commits to ensure each commit addresses a single purpose.

What are atomic commits and when do I need them in version control?▼

Atomic commits in version control are commits where each commit addresses a single purpose. You need them to maintain clean workflows, allowing for precise code review and safer handling of sensitive data by isolating logical changes during a session.

How do I selectively stage files to create clean git commits?▼

To selectively stage files for clean git commits, you review session changes and group them into logical units. This ensures temporary files are ignored, the working directory is clean, and each commit remains atomic.

Does this commit workflow handle sensitive data before committing?▼

Yes, this commit workflow handles sensitive data safely by enforcing pre-commit cleanup guidance. It ensures your environment and temporary files are ignored and your working directory is clean before composing any commit messages.

What is the best way to compose a git commit body for code review?▼

The best way to compose a git commit body for code review is to follow conventional commit formatting with a concise subject and detailed body. This provides reviewers with clear context regarding the precise changes made during the session.