skills.rest
anntnzrb
anntnzrbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

commit

Create atomic git commits with conventional commits format and staged checks.

1|Updated Jan 18, 2026
Search Tags:#git#workflow#commit#staging#code-quality#version-control#conventional-commits
One-click install
npx skills add https://github.com/anntnzrb/agents --skill commit-anntnzrb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/anntnzrb/agents/tree/main/assets/skills/commit
Command: npx skills add https://github.com/anntnzrb/agents --skill commit-anntnzrb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of creating atomic, logically separated git commits that follow project guidelines or conventional commits, improving traceability and code review.

Core Features & Use Cases

  • Atomic commits: Create one logical change per commit and avoid bundling unrelated changes.
  • Staging guidance: Use git add -p and interactive staging to selectively commit changes.
  • Workflow compliance: Follow repo guidelines, verify diffs, and output git log --oneline after commits.

Quick Start

Ask me to commit changes in your repository and I will generate atomic, conventional commits following best practices.

Frequently Asked Questions about commit

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

FAQPage Schema
What is an atomic git commit and when do I need conventional commits?▼

An atomic git commit isolates one logical change per commit to improve traceability and code review. Conventional commits format standardizes commit messages, ensuring clearly grouped changes aligned with project guidelines.

How do I create atomic git commits for unrelated staged changes?▼

Use interactive staging with git add -p to selectively stage changes, then create atomic commits by verifying diffs and enforcing repo guidelines before applying the conventional commits format.

What's the best way to enforce conventional commits format in my workflow?▼

Enforce conventional commits format by verifying staged diffs against repo guidelines, ensuring each commit represents one logical change, and outputting git log --oneline to confirm a concise commit history.

Can I selectively commit changes from a single file using interactive staging?▼

Yes, interactive staging with git add -p lets you selectively commit portions of a file, ensuring each atomic commit contains only the relevant changes and avoiding bundled, unrelated modifications.

Does this workflow support verifying diffs before applying a conventional commit?▼

Yes, the workflow verifies staged diffs before applying a conventional commit, ensuring the changes comply with repo guidelines and producing a concise commit history via git log --oneline output.

Why should I avoid bundling unrelated changes into a single git commit?▼

Bundling unrelated changes harms traceability and complicates code review. Atomic commits separate logical changes, making the commit history concise and easier to verify against project guidelines.

Related Skills

Explore More Software Engineering Skills→
blakecyzeblakecyze
2

kanso-commit

Analyze the working tree and create atomic git commits with imperative messages.

Community
Intermediate
wewetv1987-cellwewetv1987-cell

git-helper

Manage Git repository status, pull, push, branch, and log operations.

Community
Basic
tgmarinhotgmarinho

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged.

Community
Intermediate
gittowergittower
413

release

Update changelog and version files from git history using semantic versioning.

Official
Advanced