wshobson/commands
Claude Code Slash Commands
A ready set of slash commands for Claude Code, split into tools for focused tasks and workflows for multi-step orchestration
Medium risk
We rate an entry medium when the tool runs code, makes network calls or reads project files. Check what exactly it does before installing.
Why this level
- The commands act on the project: generate code, run review and deploy steps
- Some workflows delegate work to multiple agents
Install
Manual install
cd ~/.claude
git clone https://github.com/wshobson/commands.gitThe commands land in ~/.claude/commands and are invoked by folder prefix, for example /tools:api-scaffold.
This is third-party code. Review the repository files before installing.
What it does
The repository adds a collection of slash commands to Claude Code, arranged into two folders. The tools folder holds single-purpose commands: scaffold an API, audit dependencies, build a deploy checklist, trace an error, write tests. The workflows folder holds multi-step scenarios that route a task through several stages and delegate to specialized agents: feature development, full review, a TDD cycle. Commands are markdown files invoked by their folder prefix, for example tools:security-scan or workflows:feature-development.
Who it is for. For developers and devops engineers who want prebuilt Claude Code commands instead of ad hoc prompts.
Good fit when
- You want one set of commands for common development tasks
- You need multi-step scenarios that delegate across agents
- You want templates for review, tests and deploy
Not a fit when
- You do not work in Claude Code
- You need one narrow skill rather than a large command set
Example request
/tools:security-scan scan the project for vulnerabilitiesLimitations
The commands target Claude Code and are invoked by folder prefix. Some workflows rely on the agent set from the author's companion repository, and individual commands assume an already configured project environment.
How to disable. Remove the cloned commands folder from ~/.claude, or delete the command markdown files you copied into the root.
Security check
- The commands act on the project: generate code, run review and deploy steps
- Some workflows delegate work to multiple agents
README in short
The README describes a set of Claude Code slash commands split into tools and workflows. Installation is a git clone of the repository into ~/.claude, commands are invoked by folder prefix, and there is an option to flatten them into the root for short names. The author notes a separate plugin marketplace in a companion repository for a more modern approach. MIT licensed.
FAQ
How do tools differ from workflows?
Tools are single-task commands; workflows carry a task through several steps and delegate to agents.
How do I call commands without the folder prefix?
Copy the markdown files from tools and workflows into the commands root, then the command is available by its short name.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything