stage-commit
The `stage-commit` command launches a background commit subagent that automatically stages and commits all working-directory changes until the repository is clean. Use this when you want to batch-process multiple file changes into coherent, logically-grouped commits without manual approval, following the ATLAS commit convention while excluding common artifacts like `.DS_Store`, build files, and secrets.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/syahiidkamil/Software-Engineer-AI-Agent-Atlas/HEAD/.claude/commands/git/stage-commit.md -o ~/.claude/commands/stage-commit.mdstage-commit.md
Launch the `commit` subagent **in the background** — call the Agent tool with `subagent_type: commit` and `run_in_background: true`.
Before passing the task, replace `{{CURRENT_MODEL}}` below with **your own current model identity** (from your environment — e.g. `Opus 4.8 (1M context)`). This keeps the commit credit accurate as the model changes, instead of hardcoding a version that goes stale.
Pass it this task:
> Run in **stage-and-commit mode**. Autonomously stage and commit every change in the working directory — no approval needed — repeating until `git status` is clean. Never stage junk: `.DS_Store`, editor/IDE files, `*.log`, build artifacts, `.env` or other secrets. If `.gitignore` doesn't already exclude them, leave them unstaged and say so. Group related changes into separate, coherent commits following the ATLAS commit convention — don't lump everything into one mega-commit. End every commit message with this trailer verbatim:
> `Co-Authored-By: Claude {{CURRENT_MODEL}} <noreply@anthropic.com>`
Don't block on it: report that the commit agent has been launched in the background and carry on. You'll be notified when it finishes.Designs feature architectures by analyzing existing codebase patterns and conventions, then providing comprehensive implementation blueprints with specific files to create/modify, component designs, data flows, and build sequences
Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development
Code review a pull request
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
Commit what is already staged — runs the commit subagent in the background, following the ATLAS commit convention.
Use this agent when you need to perform manual quality assurance testing through browser interactions. This agent uses MCP Playwright tools to navigate websites, interact with UI elements, verify functionality, and validate user flows as a human tester would. Perfect for testing new features, regression testing, validating bug fixes, or exploring application behavior. Examples:\n\n<example>\nContext: The user has just implemented a new login feature and wants to test it.\nuser: "I've added a new login form, can you test if it works correctly?"\nassistant: "I'll use the qa-manual-tester agent to test the login functionality through the browser."\n<commentary>\nSince the user needs manual testing of a new feature, use the Task tool to launch the qa-manual-tester agent to interact with the browser and verify the login flow.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to verify that a bug fix is working properly.\nuser: "I fixed the issue where the submit button wasn't working on mobile view. Can you verify?"\nassistant: "Let me launch the qa-manual-tester agent to verify the submit button works correctly in mobile view."\n<commentary>\nThe user needs manual verification of a bug fix, so use the qa-manual-tester agent to test the specific functionality through browser interaction.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to perform regression testing after code changes.\nuser: "I've refactored the checkout flow. Please test that everything still works."\nassistant: "I'll use the qa-manual-tester agent to perform comprehensive testing of the checkout flow."\n<commentary>\nSince the user needs regression testing after refactoring, use the qa-manual-tester agent to manually test the entire checkout flow.\n</commentary>\n</example>
Interview Boss about the project, then reason from first principles to design the ideal ATLAS operating identity/system-prompt for it — free to drop KISS/YAGNI/DRY/clean-architecture entirely when the project (and the LLM's own distribution) calls for a different mindset
Initialize project context — understand the project, configure conventions, and set up project rules