How do I install the Command Development skill?

Run npx skillmds@latest add lucassantana-dev/command-development in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Command Development safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Command Development?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Command Development free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Command Development?

LucasSantana-Dev (@lucassantana-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Command Development by lucassantana-dev

Name: Command Development
Rating: 4.2 (5 reviews)
Author: LucasSantana-Dev

Command Development

Use when creating, writing, or organizing slash commands. Covers frontmatter, dynamic arguments, file references, and bash execution. Commands are instructions FOR Claude, not messages TO the user.

LucasSantana-Dev Updated Aug 19, 2026 1 repo stars

File contents

Command Development for Claude Code

Critical: Commands are directives TO Claude, not messages TO the user.

# CORRECT — instruction for Claude
Review this code for SQL injection and XSS.
Provide line numbers and severity.

# INCORRECT — message to user
This command reviews your code for security.
You'll get a detailed report.

Locations

.claude/commands/ — project-specific (team-shared)
~/.claude/commands/ — personal (all projects)
plugin-name/commands/ — plugin-bundled

Subdirectories create namespaces: ci/build.md → /build (project:ci)

Frontmatter

Field	Purpose	Example
`description`	Shown in `/help`	`Review PR for security`
`allowed-tools`	Restrict tool access	`Read, Write, Bash(git:*)`
`model`	sonnet/opus/haiku	`haiku`
`argument-hint`	Document expected args	`[pr-number] [priority]`

Dynamic Arguments

Use $1, $2, $3 or $ARGUMENTS:

---
argument-hint: [pr-number] [priority]
---

Review PR #$1 with priority $2.

Bash execution inline with backticks:

Files: !`git diff --name-only`

File References

@path includes file content; ${CLAUDE_PLUGIN_ROOT} for plugin portability:

---
argument-hint: [file]
---

Review @$1 for bugs and quality.

Config: @${CLAUDE_PLUGIN_ROOT}/config.json

Example

---
description: Deploy service to environment
allowed-tools: Bash(git:*), Read
argument-hint: [service] [environment]
---

Deploy $1 to $2.

Validate environment is staging or production.

Changed files: !`git diff HEAD~1 --name-only -- packages/$1`

Review changes above, then proceed with deployment.

See REFERENCE.md for: full frontmatter catalog, conditional logic, AskUserQuestion patterns, complex examples.

---name: command-developmentdescription: Use when creating, writing, or organizing slash commands. Covers frontmatter, dynamic arguments, file references, and bash execution. Commands are instructions FOR Claude, not messages TO the user.---# Command Development for Claude Code**Critical: Commands are directives TO Claude, not messages TO the user.**```markdown# CORRECT — instruction for ClaudeReview this code for SQL injection and XSS.Provide line numbers and severity.# INCORRECT — message to userThis command reviews your code for security.You'll get a detailed report.```## Locations- `.claude/commands/` — project-specific (team-shared)- `~/.claude/commands/` — personal (all projects)- `plugin-name/commands/` — plugin-bundledSubdirectories create namespaces: `ci/build.md` → `/build (project:ci)`## Frontmatter| Field | Purpose | Example ||-------|---------|---------|| `description` | Shown in `/help` | `Review PR for security` || `allowed-tools` | Restrict tool access | `Read, Write, Bash(git:*)` || `model` | sonnet/opus/haiku | `haiku` || `argument-hint` | Document expected args | `[pr-number] [priority]` |## Dynamic ArgumentsUse `$1`, `$2`, `$3` or `$ARGUMENTS`:```markdown---argument-hint: [pr-number] [priority]---Review PR #$1 with priority $2.```Bash execution inline with backticks:```markdownFiles: !`git diff --name-only````## File References`@path` includes file content; `${CLAUDE_PLUGIN_ROOT}` for plugin portability:```markdown---argument-hint: [file]---Review @$1 for bugs and quality.Config: @${CLAUDE_PLUGIN_ROOT}/config.json```## Example```markdown---description: Deploy service to environmentallowed-tools: Bash(git:*), Readargument-hint: [service] [environment]---Deploy $1 to $2.Validate environment is staging or production.Changed files: !`git diff HEAD~1 --name-only -- packages/$1`Review changes above, then proceed with deployment.```---**See REFERENCE.md for:** full frontmatter catalog, conditional logic, AskUserQuestion patterns, complex examples.

Frequently asked questions