Discover and install the best Claude Code commands. Browse 43 curated commands with one-click installation.
Claude Code Commands are custom slash commands that add new capabilities to your Claude Code CLI. They provide
quick, targeted functionality for common developer tasks: running tests, analyzing code, generating documentation, managing git workflows, and much more.
Commands are the simplest way to extend Claude Code. Each command maps to a specific action or workflow that you
can invoke with a short slash command (like /test, /deploy, or /docs). They’re
perfect for tasks you repeat frequently and want to standardize across your team.
This directory features the most useful Claude Code commands curated for 2026. Every command
has been reviewed for quality and includes clear usage instructions. Filter by category to find commands for git operations, testing, code analysis, deployment,
and more.
Installing a command takes seconds. Copy the install command, run it in your terminal, and the new slash command
is immediately available in your Claude Code sessions. Commands are lightweight, fast, and designed to integrate
seamlessly with your existing development workflow.
The command ecosystem thrives on community contributions. Developers worldwide are creating and sharing commands
that solve real problems. Submit your own command to help other developers streamline their
workflows and get your tool featured in our directory.
🔍
⭐ Popular
🕑 Newest
🔤 A – Z
43 commands found
Sorted by Popular
CodeAnalysis ⚡
/svelte:a11y
Audit and improve accessibility in Svelte/SvelteKit applications, ensuring WCAG compliance and inclusive user experiences.
This document provides quality guidelines, writing style recommendations, common pitfalls, and a detailed template structure for creating effective slash commands.
A comprehensive skill for creating optimized, agent-executable slash commands in Claude Code. This skill guides you through the entire process of designing, implementing, and testing reusable workflow
Provide a comprehensive command reference for penetration testing tools including network scanning, exploitation, password cracking, and web application testing. Enable quick command lookup during sec
Frequently Asked Questions about Claude Code Commands
Commands are custom slash commands you can add to Claude Code CLI. They provide quick, standardized access to specific workflows like running tests, generating docs, deploying code, or analyzing code quality.
Once installed, type the command’s slash shortcut in your Claude Code session. For example, if you install a test command, you might use /test to run your project’s test suite with intelligent configuration.
Yes, most commands are configurable. You can modify their behavior through settings files or by editing the command’s source code directly. Community commands are open source and designed to be customizable.
Commands in this directory are tested on macOS, Linux, and Windows. Some commands that rely on system-specific tools may have platform requirements, which are noted in their descriptions.
Commands are AI-aware — they understand your project context, can make intelligent decisions, and produce structured output. A shell alias runs a fixed command, while a Claude Code command adapts to your specific project and situation.
Yes, commands can be composed into workflows. You can create meta-commands that call multiple sub-commands in sequence, or use agents to orchestrate complex multi-command workflows.
{
“@context”: “https://schema.org”,
“@type”: “FAQPage”,
“mainEntity”: [
{
“@type”: “Question”,
“name”: “What are Claude Code Commands?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Commands are custom slash commands you can add to Claude Code CLI. They provide quick, standardized access to specific workflows like running tests, generating docs, deploying code, or analyzing code quality.”
}
},
{
“@type”: “Question”,
“name”: “How do I use a command after installing it?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Once installed, type the command’s slash shortcut in your Claude Code session. For example, if you install a test command, you might use /test to run your project’s test suite with intelligent configuration.”
}
},
{
“@type”: “Question”,
“name”: “Can I customize existing commands?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Yes, most commands are configurable. You can modify their behavior through settings files or by editing the command’s source code directly. Community commands are open source and designed to be customizable.”
}
},
{
“@type”: “Question”,
“name”: “Do commands work in all operating systems?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Commands in this directory are tested on macOS, Linux, and Windows. Some commands that rely on system-specific tools may have platform requirements, which are noted in their descriptions.”
}
},
{
“@type”: “Question”,
“name”: “How do commands differ from shell aliases?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Commands are AI-aware — they understand your project context, can make intelligent decisions, and produce structured output. A shell alias runs a fixed command, while a Claude Code command adapts to your specific project and situation.”
}
},
{
“@type”: “Question”,
“name”: “Can I chain multiple commands together?”,
“acceptedAnswer”: {
“@type”: “Answer”,
“text”: “Yes, commands can be composed into workflows. You can create meta-commands that call multiple sub-commands in sequence, or use agents to orchestrate complex multi-command workflows.”
}
}
]
}
(function() {
var activeCat = ‘all’;
window.ecoFilter = function() {
var query = document.getElementById(‘eco-search’).value.toLowerCase().trim();
var cards = document.querySelectorAll(‘#eco-grid > div[data-name]’);
var visible = 0;
cards.forEach(function(card) {
var name = (card.getAttribute(‘data-name’) || ”).toLowerCase();
var desc = (card.getAttribute(‘data-desc’) || ”).toLowerCase();
var cat = (card.getAttribute(‘data-cat’) || ”).toLowerCase();
var matchSearch = !query || name.indexOf(query) !== -1 || desc.indexOf(query) !== -1;
var matchCat = activeCat === ‘all’ || cat === activeCat.toLowerCase();
if (matchSearch && matchCat) {
card.style.display = ”;
visible++;
} else {
card.style.display = ‘none’;
}
});
document.getElementById(‘eco-count-num’).textContent = visible;
document.getElementById(‘eco-no-results’).style.display = visible === 0 ? ‘block’ : ‘none’;
};
