How do I install the Atomic Commits skill?

Run npx skillmds add majiayu000/atomic-commits in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Atomic Commits skill do?

Create atomic commits grouped by logical features with README.md and CLAUDE.md awareness. It is listed under Coding & Dev Tools on SkillMD.

Is Atomic Commits safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Atomic Commits?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Atomic Commits free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Atomic Commits?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Atomic Commits by majiayu000 — Agent Skill

Name: Atomic Commits
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Atomic Commits with Documentation Awareness

Guidelines for creating well-organized commits with README.md and CLAUDE.md awareness.

Documentation Check

Before committing, evaluate if changes need documentation updates.

README.md (User-facing documentation)

Change Type	README Section to Update
New commands or features	Commands/Usage documentation
CLI interface changes	Usage examples
Configuration changes	Configuration/Environment sections
Breaking API changes	Upgrade/migration notes
New features	Feature documentation
Installation changes	Installation section

Trigger files (project-specific - customize in your .claude/skills/):

src/cli.ts or src/index.ts - Entry points
.claude-plugin/plugin.json - Plugin metadata
commands/*.md - Command definitions

CLAUDE.md (Claude Code memory - hierarchical)

CLAUDE.md stores context that helps future sessions "do the right thing". Update when:

You struggled with something and the insight would prevent future mistakes
Important patterns or conventions that aren't obvious from code alone
Workflows or commands that are non-trivial to discover

CLAUDE.md is hierarchical - use the directory level matching the changed files. Use @path/to/file includes to stay DRY.

Change Scope	Which CLAUDE.md
Project-wide (scripts, CI/CD, build)	Root CLAUDE.md
Directory-specific patterns	Subdirectory CLAUDE.md (create if needed)

Grouping Rules

Identify logical features by grouping related files:

Same feature = same commit
Infrastructure/config = separate commit
Tests = with their implementation OR separate if test-only

Commit Message Format

<type>(<scope>): <description>

Types: feat, fix, docs, chore, refactor, test, style, build, ci, perf

Note: Commit messages are validated by commitlint (conventional commits format).

---name: atomic-commitsdescription: Create atomic commits grouped by logical features with README.md and CLAUDE.md awareness.--- # Atomic Commits with Documentation Awareness Guidelines for creating well-organized commits with README.md and CLAUDE.md awareness. ## Documentation Check Before committing, evaluate if changes need documentation updates. ### README.md (User-facing documentation) | Change Type | README Section to Update | |-------------|-------------------------| | New commands or features | Commands/Usage documentation | | CLI interface changes | Usage examples | | Configuration changes | Configuration/Environment sections | | Breaking API changes | Upgrade/migration notes | | New features | Feature documentation | | Installation changes | Installation section | **Trigger files (project-specific - customize in your .claude/skills/):** - `src/cli.ts` or `src/index.ts` - Entry points - `.claude-plugin/plugin.json` - Plugin metadata - `commands/*.md` - Command definitions ### CLAUDE.md (Claude Code memory - hierarchical) CLAUDE.md stores context that helps future sessions "do the right thing". Update when: - You struggled with something and the insight would prevent future mistakes - Important patterns or conventions that aren't obvious from code alone - Workflows or commands that are non-trivial to discover CLAUDE.md is hierarchical - use the directory level matching the changed files. Use `@path/to/file` includes to stay DRY. | Change Scope | Which CLAUDE.md | |--------------|-----------------| | Project-wide (scripts, CI/CD, build) | Root CLAUDE.md | | Directory-specific patterns | Subdirectory CLAUDE.md (create if needed) | ## Grouping Rules Identify logical features by grouping related files: - Same feature = same commit - Infrastructure/config = separate commit - Tests = with their implementation OR separate if test-only ## Commit Message Format ```text <type>(<scope>): <description> ``` Types: `feat`, `fix`, `docs`, `chore`, `refactor`, `test`, `style`, `build`, `ci`, `perf` **Note:** Commit messages are validated by commitlint (conventional commits format).

Frequently asked questions