How do I install the Commit skill?

Run npx skillmds@latest add jimweller/commit 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 Commit skill do?

Create an atomic conventional commit with AI context tracking It is listed under Coding & Dev Tools on SkillMD.

Is Commit safe to use?

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

Which AI agents work with Commit?

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 Commit free to use?

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

Who published Commit?

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

Commit by jimweller — Agent Skill

Name: Commit
Author: jimweller

File contents

STARTER_CHARACTER = 📌

Commit Changes

Process

1. Review Changes

git status
git diff HEAD
git diff --stat HEAD

Check for new untracked files:

git ls-files --others --exclude-standard

2. Stage Files

Add the untracked and changed files relevant to the current work.

Do NOT stage:

.env or credential files
Large binary files
Files unrelated to the current task

3. Create Commit

Write an atomic commit message with a conventional commit tag:

feat: -- New capability or feature
fix: -- Bug fix
refactor: -- Code restructure without behavior change
docs: -- Documentation only
test: -- Test additions or fixes
chore: -- Build, CI, tooling changes
perf: -- Performance improvement

For monorepo changes spanning multiple packages, note the primary package in the scope:

feat(workflows): add DAG condition evaluator
fix(web): resolve SSE reconnection on navigation
refactor(isolation): simplify worktree resolution order

Commit message format:

tag(scope): concise description of what changed

[Optional body explaining WHY this change was made,
not just what changed. Include context changes that aren't
obvious from the diff.]

[Optional: Fixes #123, Closes #456]

4. Capture AI Context Changes

If any AI context assets were modified in this commit, add a Context: section to the commit body:

feat(orchestrator): add retry logic for session recovery

Added exponential backoff when SDK subprocess crashes mid-session.
Previously a single crash would fail the entire workflow.

Context:
- Updated .claude/rules/orchestrator.md with retry conventions
- Added .claude/commands/debug-session.md for session state inspection
- Surfaced issue: mock.module() in retry tests needs isolated batch

Fixes #482

What counts as AI context changes:

.claude/rules/ -- on-demand conventions added, updated, or removed
.claude/commands/ -- slash commands created or modified
.claude/skills/ -- slash commands created or modified
.llmdocs/ -- reference docs added or updated
CLAUDE.md -- global rules changes
**/CLAUDE.md -- folder local rules changes

Git log is long-term memory for future sessions.

---name: commitdescription: Create an atomic conventional commit with AI context tracking---STARTER_CHARACTER = 📌# Commit Changes## Process### 1. Review Changes```bashgit statusgit diff HEADgit diff --stat HEAD```Check for new untracked files:```bashgit ls-files --others --exclude-standard```### 2. Stage FilesAdd the untracked and changed files relevant to the current work.**Do NOT stage:**- `.env` or credential files- Large binary files- Files unrelated to the current task### 3. Create CommitWrite an atomic commit message with a conventional commit tag:- `feat:` -- New capability or feature- `fix:` -- Bug fix- `refactor:` -- Code restructure without behavior change- `docs:` -- Documentation only- `test:` -- Test additions or fixes- `chore:` -- Build, CI, tooling changes- `perf:` -- Performance improvement**For monorepo changes spanning multiple packages**, note the primary package in the scope:```textfeat(workflows): add DAG condition evaluatorfix(web): resolve SSE reconnection on navigationrefactor(isolation): simplify worktree resolution order```**Commit message format:**```texttag(scope): concise description of what changed[Optional body explaining WHY this change was made,not just what changed. Include context changes that aren'tobvious from the diff.][Optional: Fixes #123, Closes #456]```### 4. Capture AI Context ChangesIf any AI context assets were modified in this commit, add a `Context:` section to the commit body:```textfeat(orchestrator): add retry logic for session recoveryAdded exponential backoff when SDK subprocess crashes mid-session.Previously a single crash would fail the entire workflow.Context:- Updated .claude/rules/orchestrator.md with retry conventions- Added .claude/commands/debug-session.md for session state inspection- Surfaced issue: mock.module() in retry tests needs isolated batchFixes #482```**What counts as AI context changes:**- `.claude/rules/` -- on-demand conventions added, updated, or removed- `.claude/commands/` -- slash commands created or modified- `.claude/skills/` -- slash commands created or modified- `.llmdocs/` -- reference docs added or updated- `CLAUDE.md` -- global rules changes- `**/CLAUDE.md` -- folder local rules changesGit log is long-term memory for future sessions.

Frequently asked questions

Commit