skills.rest
ramonclaudio
ramonclaudioCOMMUNITY
Explore all skills by this author →
Website𝕏@ramonclaudioGitHub

commit

Convert staged changes into atomic conventional commits with optional GPG signing.

4|Updated Jan 31, 2026
Search Tags:#git#workflow#commit#pull-request#conventional-commits#atomic
One-click install
npx skills add https://github.com/ramonclaudio/skills --skill commit-ramonclaudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/ramonclaudio/skills/tree/main/plugins/commit/skills/commit
Command: npx skills add https://github.com/ramonclaudio/skills --skill commit-ramonclaudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces atomic commits using a conventional format to produce clean, auditable git histories and safer rollbacks.

Core Features & Use Cases

  • Atomic commits: each commit represents a single logical change.
  • Conventional commits: enforces type(scope): description to standardize messages.
  • GPG signing: signs commits automatically when configured.
  • Guided workflow: supports analyze, commit, verify, and optional PR/merge flows.
  • Use cases: safer production deployments, easier code reviews, and clear change audits.

Quick Start

Use this skill to turn your current staged changes into atomic commits that follow the conventional format. If you want to push and open a PR, use --pr; for a direct push, use --push; for merging a PR, use --merge PR#.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I make atomic git commits that follow the conventional commit format?▼

Atomic conventional commits isolate staged changes into individual logical updates formatted as type(scope): description, ensuring auditable history and safe rollbacks.

What is the best way to split grouped git changes into safe, rollback-ready commits?▼

Splitting grouped changes into atomic commits isolates each logical update, yielding clear audit records and safer production rollbacks.

Can I automatically sign my conventional commits with GPG during the workflow?▼

Yes, GPG signing is supported; the Skill automatically signs atomic commits when GPG is configured in your environment.

How do I push commits and open a pull request after staging changes?▼

Use the --pr flag to push atomic commits and open a pull request; use --push for direct pushes, and --merge PR# to merge pull requests.

How do I analyze staged changes before committing them to git?▼

Use the --analyze flag to review staged changes and determine how to split them into atomic conventional commits.

When do I need atomic commits for my software development workflow?▼

Atomic commits are needed for software development workflows requiring auditable history, safe rollbacks, and clear change records across local and collaborative work.

Related Skills

Explore More Software Engineering Skills→
Harvest-Forged-CodeHarvest-Forged-Code
10

git-commit

Enforce GPG-signed Git commits with semantic messages and file-change tables.

Official
Advanced
dtbuchholzdtbuchholz

commit-push-pr

Stage Git changes, create conventional commits, push branches, and open pull requests via GitHub CLI.

Community
Intermediate
hypeJunctionhypeJunction
1

git-conventions

Enforce Git branch naming and Conventional Commits for CI/CD pipelines.

Community
Intermediate
pigfootpigfoot
5

commit

Generate conventional Git commits with emoji prefixes and GPG signing.

Community
Advanced