atomic-commits

Creates atomic conventional commits on feature branches and ships them via pull requests.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/arndvs/ctrlshft --skill atomic-commits-arndvs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: atomic-commits
Source: https://github.com/arndvs/ctrlshft/tree/main/skills/atomic-commits
Command: npx skills add https://github.com/arndvs/ctrlshft --skill atomic-commits-arndvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI-assisted coding sessions often end with a pile of uncommitted changes dumped into a single vague commit, or worse, committed directly to main. This Skill enforces disciplined version control: one logical change per commit, conventional commit messages, feature-branch isolation, and a gated push-and-PR workflow. ## Core Features & Use Cases - Commit Mode: Surveys the diff, groups changes into logical units, and stages each unit separately (including partial staging with git add -p) to produce clean atomic commits with conventional messages. - Ship Mode: Extends Commit mode with base-branch resolution, rebase, a four-part pre-push gate (branch safety, base verification, quality gates, secret scan), push, and PR creation via the gh CLI. - Copilot Review Request: Automatically requests a Copilot pull request review after PR creation, with REST API verification and retry fallbacks. - Use Case: After finishing a multi-file feature, ask the agent to "ship this work" — it creates an ai/feat/... branch, splits the diff into atomic commits, rebases onto the verified base branch, runs tests and a secret scan, pushes, and opens a PR ready for review. ## Quick Start Ask the agent to commit my current changes as atomic commits, or say "ship this" to also push and open a pull request.

Frequently Asked Questions about atomic-commits

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

FAQPage Schema
How do I make atomic commits with conventional commit messages?▼

Survey the full diff with git status and git diff, group changes into logical units, then stage and commit each unit separately using git add for specific files or git add -p for partial staging. Each commit message follows the type(scope): summary format like feat(auth): add token rotation.

What is the difference between Commit mode and Ship mode?▼

Commit mode only creates atomic commits on a feature branch, used for checkpoints during multi-slice work. Ship mode adds rebasing onto the base branch, pre-push gates, pushing, PR creation, and requesting a Copilot review when the work is ready for review.

How do I create a GitHub pull request from the command line?▼

Use the GitHub CLI with gh pr create, passing --base for the target branch, --title in conventional commit format, and --body summarizing changes and verification steps. The Skill resolves the base branch authoritatively via a verify script before creating the PR.

Why should I never commit directly to main or master?▼

Committing to base branches bypasses review and risks breaking shared code. The Skill enforces feature branches named ai/<type>/<description>, so all changes flow through a pull request with quality gates and review before merging.

What checks run before pushing a branch?▼

Four gates run before push: confirming you are not on a base branch, verifying the branch ancestry against the authoritative PR base, running the repo's tests and lint, and scanning the diff for secrets like private keys or tokens. Push aborts if any gate fails.

How do I request a Copilot code review on a pull request?▼

Run gh pr edit <PR_NUMBER> --add-reviewer copilot-pull-request-reviewer, then verify via the REST pulls endpoint that a Copilot bot login appears in requested_reviewers. Avoid posting @copilot review comments, which can trigger the wrong Copilot task flow.