Review a Claude Code slash command and recommend improvements based on best practices
Analyzes a Claude Code slash command against official best practices and provides prioritized improvement recommendations. Use this when you've created a new command and want to ensure it follows proper structure, security, and usability guidelines before sharing or using it.
/plugin marketplace add sjungling/claude-plugins/plugin install claude@claude-pluginspath-to-command.mdReview the Claude Code slash command located at: $1
First, fetch the official documentation from https://docs.claude.com/en/docs/claude-code/slash-commands.md to understand current best practices.
Then read the command file and analyze it for conformance to best practices. Provide actionable recommendations for improvements.
Focus on:
Frontmatter Quality:
description field (clear, concise explanation)argument-hint for auto-completion guidanceallowed-tools specification (explicit permissions vs. inherited)model specification if needed for specific Claude modelsdisable-model-invocation if command shouldn't be auto-invokedArgument Handling:
$1, $2 positional parameters vs $ARGUMENTSCommand Focus:
Writing Style:
Tool Permissions:
Documentation Quality:
Provide prioritized, specific recommendations organized by:
For each recommendation:
Highlight what the command does well and offer to implement improvements if requested.
If the command file path is not provided, search for .md files in .claude/commands/ in the current working directory and offer to review them.