[DOCS] Slash commands documentation incorrectly shows $1, $2, $3 positional parameters

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://docs.claude.com/en/docs/claude-code/slash-commands

Section/Topic

https://docs.claude.com/en/docs/claude-code/slash-commands#arguments

Current Documentation

## Bug Description

The Slash Commands documentation
contains an example showing positional parameters ($1, $2, $3) that do not actually work
in practice.

## Documentation Claims

The docs state:
> "Access specific arguments individually using positional parameters (similar to shell
scripts)"

With this example:
```markdown
# Command definition
echo 'Review PR #$1 with priority $2 and assign to $3' > .claude/commands/review-pr.md

# Usage
> /review-pr 456 high alice
# $1 becomes "456", $2 becomes "high", $3 becomes "alice"

Actual Behavior

Testing shows that $1, $2, $3 do NOT work - they remain as literal strings instead of being
replaced.

Test command: .claude/commands/test-arguments.md
Review PR #$1 with priority $2 and assign to $3

Result:

• Variables remain literal: Review PR #$1 with priority $2 and assign to $3
• Only $ARGUMENTS works (returns all arguments as single string)

Evidence

GitHub Issue #4370 confirms the current implementation:
"Currently uses a single $ARGUMENTS placeholder"

This feature request to add structured argument support wouldn't exist if $1, $2, $3 already
worked.

Expected Resolution

Either:

1. Fix documentation - Remove the incorrect example and clarify that only $ARGUMENTS is

supported

1. Implement the feature - Make $1, $2, $3 actually work as documented

Environment

• Claude Code version: Latest (as of 2025-10-02)
• Platform: Windows
• Test repository: Local .claude/commands/ directory

Related Issues

• #4370 - Feature request for structured argument definitions

Labels to add: documentation

What's Wrong or Missing?

individual arguments $1 $2 etc are not working

Suggested Improvement

make them work

Impact

High - Prevents users from using a feature

Additional Context

_No response_