commit

Stage and commit code changes with atomic conventional commit messages.

1|Updated Mar 2, 2026

Search Tags:#git #code review #version control #commit #conventional commits #atomic commits

Ready to run

npx skills add https://github.com/sjev/robodev --skill commit-sjev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of committing code changes by enforcing atomic commits and conventional commit message formats, ensuring a clean and understandable Git history.

Core Features & Use Cases

Atomic Commits: Groups related changes into single, focused commits.
Conventional Commits: Enforces a standardized format for commit messages (type(scope): description).
Branch Safety: Prevents direct commits to main/master branches.
Use Case: After implementing a new feature, use this skill to create separate commits for the backend logic, frontend adjustments, and updated tests, each with a clear and descriptive message.

Quick Start

Use the commit skill to stage and commit the changes in src/utils.py with the message "fix(auth): resolve login bug".

Frequently Asked Questions about commit

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

FAQPage Schema

How do I enforce atomic commits and conventional commit messages in Git?▼

To enforce atomic commits and conventional commit messages, this Skill stages and commits code changes using a standardized `type(scope): description` format. It guides you through grouping related changes into single, focused commits to ensure a clean Git history.

Can I commit directly to my main or master branch using this approach?▼

No, you cannot commit directly to main or master branches. This approach enforces branch safety by preventing direct commits to protected branches and requires you to stage and commit changes on a feature branch instead.

What is the best way to separate backend logic and frontend adjustments into different commits?▼

The best way to separate changes is using atomic commits. This process groups related changes into single, focused commits, allowing you to create separate entries for backend logic, frontend adjustments, and tests with clear descriptions.

Do I need the Git CLI installed to stage and commit code with conventional formats?▼

Yes, you need the Git CLI installed to use this commit process. The Skill requires the Git CLI to stage and commit code changes on a feature branch while enforcing the defined conventional commit message structure.

How does the conventional commit format improve version control history?▼

The conventional commit format improves version control history by enforcing a standardized `type(scope): description` structure. This creates a clean and understandable Git history by ensuring every atomic commit has a clear, descriptive message.