Skip to documentation
Documentation
Documentation
OverviewInstallationQuickstartConfigurationTroubleshootingFAQ

Usage

Terminal interfaceCLIDashboardAnalytics

Collaborate

ArtifactsSession sharingBlueprintsAgent identitiesMCP server

Configure

AgentsSkillsRulesCommandsInheritancePlaybooksExperimentsHooksTeamWorkspaces

API Reference

API OverviewAuthenticationSessions APIResources APIOrganizations APIProjects APIPlaybooks APIExperiments API
Need a hand?Find an answer in troubleshooting.
Loading docs…
CREWKIT / DOCUMENTATION

Commands

Custom slash commands for Claude Code.

Commands are custom slash commands that appear in Claude Code. They provide shortcuts for common workflows.


Create a command

Create a markdown file in .claude/commands/ (or through the dashboard):

---
name: deploy-check
description: Verify deployment readiness
---

Check the following before deployment:

1. All tests pass
2. No TODO comments in changed files
3. Database migrations are reversible
4. Environment variables are documented
5. No secrets in source code

Using commands

Commands appear as slash commands in Claude Code:

/deploy-check

Claude reads the command file and follows its instructions.


Command file format

Commands use the same markdown + optional frontmatter format as other resources:

---
name: quick-test
description: Run tests for changed files only
---

Identify which test files correspond to the files I've changed
in this git branch, then run only those tests.

Sync and tiers

Commands sync to .claude/commands/ and support the same three-tier inheritance as agents, skills, and rules. See Inheritance.


Next steps

  • Agents
  • Skills
  • Inheritance

Rules

Path-based rules that auto-load context for Claude Code.

Inheritance

How resources merge across platform, organization, and project tiers.

On this page

Create a commandUsing commandsCommand file formatSync and tiersNext steps