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.Activate ATLAS pattern recognition mode. Identify repeated patterns, extract essential characteristics, and create reusable abstractions from concrete examples.
Adversarially review something just built — presume it is broken and find where. Use after implementing a feature, finishing a build, or before shipping, or whenever ATLAS or Boss wants a hostile second opinion on a diff, a running app, or a whole codebase. Spawns clean-context reviewers with opposing lenses (correctness, security, empty-world) and reproduces every finding by running the target before believing it. Distinct from /code-review, which statically reads a diff and never runs the app.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Stop and consult this skill whenever your response would include specific facts about Anthropic's products. Covers: Claude Code (how to install, Node.js requirements, platform/OS support, MCP server integration, configuration), Claude API (function calling/tool use, batch processing, SDK usage, rate limits, pricing, models, streaming), and Claude.ai (Pro vs Team vs Enterprise plans, feature limits). Trigger this even for coding tasks that use the Anthropic SDK, content creation mentioning Claude capabilities or pricing, or LLM provider comparisons. Any time you would otherwise rely on memory for Anthropic product details, verify here instead — your training data may be outdated or wrong.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
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
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