Claude Dev Toolkit plugin
A set of slash commands, hooks and subagents for Claude Code: tests, quality, security, git and docs through an npm package.
- 111 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Commands run shell commands, edit project files and make commits and pushes.
- Hooks attach to Claude Code events and install dependencies.
Install
- Works in
Manual install
npm install -g @paulduvall/claude-dev-toolkit
claude-commands install --activeInstalls the package and 17 core commands; `claude-commands install --all` installs all 45.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Commands run shell commands, edit project files and make commits and pushes.
- Hooks attach to Claude Code events and install dependencies.
This is third-party code. Review the repository files before installing.
What it does
The PaulDuvall/claude-code repository extends Claude Code with slash commands, hooks and subagents. Commands install globally through the npm package `@paulduvall/claude-dev-toolkit` and work in any project on the machine. Main commands: `/xtest` runs tests and computes coverage, `/xquality` checks and fixes formatting, imports and types, `/xsecurity` looks for vulnerabilities and secrets, `/xgit` handles commit and push, `/xdebug` analyzes errors together with a subagent, `/xdocs` updates documentation, `/xrefactor` finds code smells, `/xtdd` drives a red-green-refactor cycle and `/xspec` writes machine-readable specifications. `/xhelp` suggests which one to choose. There are settings templates, a `claude-commands oidc` subcommand for AWS OIDC setup, 25 specialized subagents and a four-tier model of checking hooks.
Who it is for. Claude Code developers who want ready commands for routine work: tests, checks, commits and documentation.
Good fit when
- You want to run tests with one command and get coverage with smart defaults.
- Before review you want a pass over code quality, security and documentation.
- Work follows TDD and the red, green, refactor, commit cycle should run automatically.
- You want a hint about which command fits a task.
Not a fit when
- The project has no git history, so edits cannot be rolled back.
- You need one narrow skill rather than a set of dozens of commands.
- Company policy forbids global npm packages.
Example request
Run /xquality fix and /xtest coverage, then show the project summary and prepare a commit through /xgit without pushing.Limitations
The commands run the shell, edit files, make commits and pushes and install dependencies, so the README advises reading the source first, starting with individual commands and trying in a disposable environment. A devcontainer is provided for autonomous work. Installation needs Node and npm. Of 45 commands, 17 are active and the rest experimental, and they may change. The README advises keeping git history clean so edits roll back easily and reading each command with `/x<name> help` before running it.
How to disable. Remove the package with `npm uninstall -g @paulduvall/claude-dev-toolkit` and the installed commands from the Claude Code commands directory. Disable hooks in Claude Code settings.
FAQ
How do I install the toolkit?
Run `npm install -g @paulduvall/claude-dev-toolkit`, then `claude-commands install --active` for the 17 core commands or `claude-commands install --all` for all 45.
How do I install the subagents?
Run `claude-commands subagents --install`: it adds 25 specialized subagents, for example for debugging.
What does /xsecurity do?
It scans for vulnerabilities and secrets with project maturity in mind. A quick check for leaked credentials runs as `/xsecurity secrets`.
How do I configure settings?
Run `claude-commands config --template basic-settings.json`; for stricter protection use `security-focused-settings.json`, and for full features `comprehensive-settings.json`.
Is it safe to run the commands?
They run shell commands, change files and make commits. The author advises reading the source, starting with one command and trying the set in a sandbox or devcontainer.
Discussion
No questions or reviews yet.
Related
PluginsA set of slash commands, skills and subagents for Claude Code: review, tests, security, releases, docs and GitHub to Linear sync
One-command Claude Code environment installer: a wizard sets up agents, rules, commands, skills and hooks in three profiles
A set of Claude Code utilities: background skills, expert agents, slash commands and prompt templates for development
A Claude Code plugin: 39 commands for PRs, review, commits and specs, nine expert roles and hooks, in eight language versions
A ready-made Claude Code setup: agents, slash commands, skills, safety hooks, rules and MCP connections in one install
Plugins for git, Python and accessibility in one place: 400+ skills, subagents and hooks against dangerous agent commands.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Claude Dev Toolkit (this card) | no | 111 | |
| Claude Code Templates | no | 33,413 | a catalog of templates for many tasks; Claude Dev Toolkit installs its own set of `/x…` commands with hooks as one package |
| Awesome Claude Code Subagents | no | 26,506 | a collection of subagents; here subagents come together with commands and hooks |
README in short
The repository publishes command sources in `slash-commands/active`, hook scripts in `hooks` and the npm package in `claude-dev-toolkit`. Every command has built-in help, for example `/xtest help`.