commit

Generate conventional commit messages and stage Git changes atomically.

69|3|Updated Feb 5, 2026

Search Tags:#automation #git #workflow #commit #staging #code-quality #conventional-commits

Ready to run

npx skills add https://github.com/PaulRBerg/agent-skills --skill commit-paulrberg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/PaulRBerg/agent-skills/tree/main/skills/commit
Command: npx skills add https://github.com/PaulRBerg/agent-skills --skill commit-paulrberg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the tedious and error-prone process of crafting Git commit messages and managing staged changes, ensuring consistency with conventional commits and improving traceability.

Core Features & Use Cases

Atomic commits: Stages and commits only the changes from the current session or all changes with a single flag.
Conventional-commit formatting: Infers or accepts a type and generates a compliant subject line and body.
Workflow integration: Optional push or Graphite-based submission for team-wide automation.

Quick Start

Use the commit skill to create an atomic commit from the current workspace. Example: run the skill with --all to commit all changes, --deep for detailed analysis, and --push to push after committing.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I automate commit messages with conventional commits format?▼

Conventional commits format standardizes commit messages with a type, scope, and subject line. This Skill automates message generation by analyzing your diffs, inferring the commit type, and composing a compliant message body, ensuring consistency across your repository.

What's the best way to create atomic commits in Git?▼

Atomic commits isolate single logical changes, improving traceability and code review. This Skill stages and commits only current session changes, or all changes with the --all flag, ensuring each commit represents one cohesive unit of work.

Can I automatically push commits after staging and committing?▼

Yes, the --push flag integrates push submission directly into the commit workflow. The Skill also supports Graphite-based submission and stack-oriented options like --deep and --stack for team automation pipelines.

How does conventional commit analysis improve code quality?▼

Conventional commits enforce consistent message structure and categorization, making diffs predictable and searchable. This Skill heuristically infers commit type and scope from your changes, reducing manual effort and enforcing standards automatically.

Do I need to manually stage changes before using this Skill?▼

No, the Skill manages staging automatically. It stages only current session changes by default, or uses --all to include all modifications, eliminating manual staging steps while maintaining atomic, well-formed commits.

Can this Skill work with existing Git workflows?▼

Yes, it integrates into development workflows requiring atomic commits and conventional messaging. The Skill applies to any repository using Git and supports optional integration with push flags and Graphite-based team submission systems.