Skip to main content
command CX Codex

stage-commit — Claude Code command: commits and setup

The stage-commit command hands working-directory changes to a background commit subagent. Use it to create grouped commits and keep going until Git reports a clean tree.

no license ★ 406 updated 2026-06-25

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/stage-commit.md
Open on GitHub

What stage-commit does

Run /stage-commit to start the commit subagent in the background. It stages eligible changes and makes separate commits for related work, repeating the process until git status shows a clean tree. The command does not wait for the agent to finish.

The agent keeps secrets, IDE files, logs, build outputs, and .DS_Store out of commits. When .gitignore does not exclude those files, it leaves them unstaged and reports that. Each commit message gets a trailer naming the current model, so that identity must be substituted before the task is handed off.

What it helps with

  • Commit eligible changes across the working directory
  • Split unrelated work into coherent commits
  • Keep secrets and generated files out of the index
  • Repeat commits until Git reports a clean tree

Example prompts for the agent

  • Run /stage-commit and commit the eligible changes in this working directory.
  • Group related edits into separate commits and leave secrets unstaged.
  • Keep going until git status shows a clean tree.

How to install stage-commit

Manually: put the files in place

.claude/commands/stage-commit.md

Call it with /stage-commit. For all projects use ~/.claude/commands/

Questions about stage-commit

How do I install stage-commit in Claude Code?

Add the command file to your project at .claude/commands/stage-commit.md.

What does stage-commit do?

It launches the commit subagent in the background to stage eligible changes and make grouped commits until Git is clean.

Which files does stage-commit keep out of commits?

The agent excludes secrets, .DS_Store, editor and IDE files, logs, and build outputs. If .gitignore does not filter them, it leaves them unstaged and reports that.

Similar slash commands

All slash commands for Git and GitHub →

From the same set26

The whole set →
commit Runs a background subagent to commit staged Git changes following ATLAS conventions. Useful when you want automated commits without blocking your session. CX Codex +1 ★ 406repo stars learning-from-mistakes learning-from-mistakes — a skill that writes a bug or mistake into a separate file after the problem is resolved. Captures the cause, fix, and lesson to avoid repeating the debugging work. CX Codex +1 ★ 406repo stars log log inspects recent git commits, summarizes their themes, and maps them against uncommitted changes in your working tree. CX Codex +1 ★ 406repo stars create-test-cases create-test-cases drafts browser-focused manual test cases in Markdown for a project feature or area. Use it to prepare cases for /qa:manual-test-run. CX Codex +1 ★ 406repo stars wireframe The wireframe command renders a static low-fidelity screen layout into a single HTML file — gray boxes, dashed borders, no libraries. Opens with a double-click. CX Codex +1 ★ 406repo stars commit Creates Git commits autonomously using ATLAS conventions without asking for approval. Handles staged files or splits working changes into clean commits. CX Codex ★ 406repo stars abstraction-power The abstraction-power skill guides Claude Code from concrete code examples to reusable models by spotting their shared structure. Use it to examine duplicated logic or shape a system design. CX Codex +1 ★ 406repo stars get-to-know get-to-know is a Claude Code command that initializes project context by gathering stack, structure, and conventions, creating a project map, and configuring the environment. CX Codex +1 ★ 406repo stars

Project sponsors

Companies that keep this analytics open