Commands
Reusable slash commands that automate repeatable workflows in Claude Code.
Slash commands are reusable prompts you invoke with /name. Each is a Markdown file you drop into ~/.claude/commands — automate repeatable workflows like reviews, commits, and refactors with a single keystroke.
53 results
Audit Accessibility
Audit a component or page for accessibility against WCAG — semantics, names, keyboard, ARIA, contrast, forms, motion.
Explain Error
Diagnose an error message or stack trace and propose a fix.
Trace Data Flow
Trace how a value, field, or variable flows through the codebase from source to sink.
DB Migrate
Generate and apply a database migration the safe way — using the project's migration tool, with expand-contract discipline for breaking changes, lock-free DDL, and a reversible up/down.
Scaffold a pgvector Schema & HNSW Index
Scaffold a production-ready pgvector schema and HNSW index for a corpus — matching the project's migration tooling, distance metric, and embedding dimensions.
Seed Data
Generate realistic, referentially-consistent seed data and a re-runnable seed script from your actual schema — types and constraints respected, plausible values, FK-dependency insert order, idempotent, never aimed at production.
Add Docstrings
Add or improve docstrings for the public API of a file or symbol.
Explain Code
Explain what the given code does, in clear prose with a short summary.
Update README
Update the README to reflect the current scripts, structure, and features of the repo.
Clean Branches
Safely prune merged and stale Git branches: drop dead remote-tracking refs, list merged candidates for review, then delete with the safe -d variant.
Create PR
Push the current branch and open a GitHub pull request with a generated title and body.
Git Bisect
Drive git bisect to find the exact commit that introduced a regression.
Git Undo
Safely reverse the last Git operation in the current repo — pick the right tool (restore, reset --soft/--mixed, revert, or reflog recovery) based on what happened and whether it was already pushed, and confirm before anything destructive.
Resolve Merge Conflicts
Walk through resolving the in-progress merge, rebase, or cherry-pick conflict in the current repo by understanding both sides, then verify before continuing.
Sync Branch
Fetch and rebase the current branch onto its base, resolving conflicts and verifying the build.
Add Caching
Add a caching layer to one expensive function or endpoint correctly — confirm it's cacheable, design the cache key/TTL/layer/invalidation, handle stampedes, wrap the call in one place, and report the design.
Find N+1 Queries
Scan code read-only for N+1 query patterns — loops that query per iteration and handlers that fan out per-row — and report each with a location, why it is N+1, and the concrete eager-load/batch/set-based fix.
Profile Postgres Queries
Profile a Postgres workload to find the queries actually costing you — rank by total time with pg_stat_statements, EXPLAIN the worst offenders, and recommend the highest-leverage fix.
Set Perf Budget
Define and enforce a cost and latency budget for an LLM feature or endpoint — set p95/p99 latency and cost-per-request ceilings, instrument to measure them against real traffic, and wire a check that fails when the budget is breached.
Breakdown Task
Decompose a task into an ordered checklist of small, verifiable steps.
Estimate Effort
Produce a grounded effort and complexity estimate for a task by exploring the codebase read-only.
Plan Feature
Explore the codebase and produce an implementation plan for a feature.
Write Design Doc
Explore the codebase and write a decision-oriented design doc / RFC for a feature or system change.
Extract Function
Extract a code region into a well-named function and update the call site.
Optimize Imports
Remove unused imports and organize the rest in a file or directory per the project's conventions — preferring the project's own import tool where one is configured — without changing behavior.
Refactor
Refactor the target for readability and structure without changing behavior.
Rename Symbol
Safely rename a symbol project-wide, distinguishing the real symbol from coincidental substring matches.
Benchmark Rerankers
Measure whether adding a reranker actually improves retrieval, by scoring reranked vs. un-reranked results on a labeled query set.
Find Bug
Investigate a reported symptom, form hypotheses, and locate the root cause.
Red Team LLM
Red-team an LLM app or agent for prompt injection, jailbreaks, and data leakage — probe the real attack surface (input, RAG, tools, system prompt) with adversarial inputs and report what got through and how to fix it.
Review PR
Review a pull request for correctness, security, and style, and summarize findings.
Review Tests
Review the quality of a test suite, not just whether it passes — find weak assertions, missing edge cases, and tests coupled to implementation.
Security Scan
Scan the current diff or given paths for security vulnerabilities.
Add Human Approval Step
Scaffold a human-in-the-loop approval gate into an agent so it pauses before a consequential action and resumes after approval.
Add a Streaming LLM Endpoint
Scaffold a token-streaming LLM endpoint — server-side streaming plus the client handler — so responses render incrementally instead of after a long wait.
New Component
Scaffold a new UI component matching the project conventions.
Scaffold CLI Command
Scaffold a new subcommand for an existing CLI (or a minimal new CLI) in the project's language — flag/argument parsing, --help text, input validation, and correct exit codes — matching the framework and conventions already in use.
Scaffold Dockerfile
Scaffold a production-grade multi-stage Dockerfile and .dockerignore for the current project.
Scaffold GitHub Action
Scaffold a hardened GitHub Actions workflow for a stated goal, wired to the project's real test/lint/build commands.
Scaffold RAG Pipeline
Scaffold a Retrieval-Augmented Generation pipeline — ingestion (load, chunk, embed, upsert) and retrieval (search, rerank, grounded prompt with citations) — fitted to the project's stack.
Scaffold a vLLM Serving Config
Scaffold a vLLM serving config for a model on a target GPU — pick precision/quantization and parallelism to fit, set batching and context length, and expose an OpenAI-compatible server.
Fix Failing Test
Diagnose and fix a failing test by finding the real root cause.
Hunt Flaky Tests
Reproduce a flaky test, find the real source of nondeterminism, and fix the cause.
Generate E2E Test
Scaffold a resilient end-to-end test for a user flow grounded in the real UI.
Run Evals
Run the project's LLM evaluation suite (DeepEval, promptfoo, or RAGAS) and report scores against thresholds before a merge.
Write Tests
Generate tests covering the happy path and edge cases for the given target.
Add MCP Server
Add an MCP server to the current project the safe way — pick the transport and scope, wire secrets through env vars, vet provenance, and verify the connection before trusting it.
Create Skill
Scaffold a new Claude Code skill into .claude/skills/<name>/SKILL.md — a model-invoked capability with a trigger-rich description, scoped tools, and a lean body that pushes detail into resource files.
Create Slash Command
Scaffold a new Claude Code slash command into .claude/commands/ — a valid Markdown file with frontmatter, a least-privilege allowed-tools allowlist, and a $ARGUMENTS-driven body of numbered steps ending in a Report.
Create Subagent
Scaffold a new Claude Code subagent definition file into .claude/agents/ with a routing-ready description, scoped tools, and a system prompt.
Setup Claude CI
Wire Claude Code into this repo's CI the safe way — install the GitHub App or scaffold the workflow YAML, scope permissions to the minimum, set secrets correctly, and verify with a real trigger.
Setup Pre-commit Hooks
Set up fast pre-commit hooks that catch problems before they land — detect the repo's existing stack and hook mechanism, run lint/format/typecheck plus a secret scan on staged files only, keep the slow test suite in CI, and make the setup reproducible for the whole team.
Frequently asked questions
- What is a Claude Code slash command?
- A slash command is a reusable prompt saved as a Markdown file and invoked with /name in Claude Code. It expands into instructions Claude follows, optionally using arguments via $ARGUMENTS.
- How do I install a slash command?
- Save the command to ~/.claude/commands/<name>.md for all your projects, or .claude/commands/<name>.md inside a single project. Then type /<name> in Claude Code to run it.
- Can commands take arguments?
- Yes. Reference $ARGUMENTS in the command body and anything you type after the command name is substituted in, so one command can handle many inputs.
- Are these commands free?
- Yes. Every slash command on AgentsCamp is free to copy, download, and install, with no signup required.
- How is a command different from an agent?
- A slash command is a prompt you trigger manually with /name in your main conversation. An agent is a subagent with its own context window that Claude can delegate to automatically. Commands are quick and explicit; agents are autonomous and isolated.