atomic-commits

Enforces atomic commit workflow — breaks implementation into small, self-contained units and commits after each one.

IndexedGPL-3.0

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/kevinashworth-atomic-commits

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Enforces atomic commit workflow — breaks implementation into small, self-contained units and commits after each one. Use when implementing features, fixing bugs, or making any multi-step code changes.

Use cases: productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/atomic-commits

What's inside

Skill name: atomic-commits
Description: Enforces atomic commit workflow — breaks implementation into small, self-contained units and commits after each one. Use when implementing features, fixing bugs, or making any multi-step code changes.
License: GPL-3.0
Instructions: 30 lines in SKILL.md · view on GitHub

Agent Skills spec issues

metadata: must be a key/value mapping

Files (2)

SKILL.md
conventional-commit-message-instructions.md · references/

SKILL.md (first lines)

# Atomic Commits

Every task follows this rhythm: **plan, then repeat (implement one thing → verify → commit).**

## 1. Plan

Before coding, break the task into atomic steps. List them. Each step is one logical change — one concern, one purpose. The codebase must work after each step.

## 2. Implement → Verify → Commit (repeat for each step)

Do one step. Verify it works. Commit it. Move to the next.

**One commit = one logical change.** Not two things. Not "a feature and its tests." Not "a rename and a behavior change." One thing.

Stage only the files that belong to that change. Never `--no-verify`.

## 3. Stay honest

- If a step should split further, split it.
- If tests break from your change, fix them in the same commit — the unit isn't done until it works.
- Never amend a previous atomic commit to sneak in more changes. Make a new commit.

## Additional Resources

### Reference Files

For detailed guidance, consult:

- **`references/conventional-commit-message-instructions.md`** - commit message instructions

From kevinashworth/opencode-config, GPL-3.0.

Signals

Stars: 0
Forks: 0
Open issues: 0
Last commit (this folder): Jun 28, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License: GPL-3.0
Repository: github.com/kevinashworth/opencode-config
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from kevinashworth

Cite this page

atomic-commits skill. Agent Mart. https://agentmart.dev/skills/kevinashworth-atomic-commits (last updated 2026-10-24)