Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] Slash commands docs omit `@` file references in arguments, including absolute paths [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#52618•Fetched 2026-04-24 06:02:18
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3

Root Cause

That omission matters because the supported workflow is more specific than the current docs suggest: users can invoke a slash command and pass an @ file reference as an argument, including an absolute path. Today, readers have to infer this by stitching together separate pages about skill arguments, @ file references, and generic autocomplete.

RAW_BUFFERClick to expand / collapse

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

Pass arguments to skills, plus the file-reference guidance for slash-command workflows

Current Documentation

The slash-commands page currently says:

Both you and Claude can pass arguments when invoking a skill. Arguments are available via the $ARGUMENTS placeholder.

This skill fixes a GitHub issue by number. The $ARGUMENTS placeholder gets replaced with whatever follows the skill name:

When you run /fix-issue 123, Claude receives "Fix GitHub issue 123 following our coding standards..."

The common-workflows page separately says:

  • File paths can be relative or absolute
  • @ file references add CLAUDE.md in the file's directory and parent directories to context

The interactive-mode page separately says:

| @ | File path mention | Trigger file path autocomplete |

What's Wrong or Missing?

The docs never state that @ file references and their autocomplete work inside slash-command / skill arguments.

That omission matters because the supported workflow is more specific than the current docs suggest: users can invoke a slash command and pass an @ file reference as an argument, including an absolute path. Today, readers have to infer this by stitching together separate pages about skill arguments, @ file references, and generic autocomplete.

Changelog v2.1.119 fixed a bug in this exact workflow (@-file Tab completion inside a slash command with an absolute path), which implies this is intended product behavior and should be documented explicitly rather than left implicit.

Suggested Improvement

Add a short note and example to https://code.claude.com/docs/en/slash-commands under Pass arguments to skills, such as:

Skill arguments can include @ file references, the same way regular prompts do.

Examples:

  • /explain-code @src/auth/login.ts
  • /explain-code @/absolute/path/to/src/auth/login.ts

When you type @ while entering slash-command arguments, Claude Code can show file autocomplete suggestions there as well.

Also add a cross-reference from the file-reference guidance in common-workflows (or interactive-mode) so users can discover that @ references are supported inside slash-command arguments, not just in plain prompts.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/slash-commandsPass arguments to skills explains positional arguments but not @ file references in arguments
https://code.claude.com/docs/en/common-workflowsReference files and directories explains @ references and says file paths can be relative or absolute, but not that this also applies inside slash commands
https://code.claude.com/docs/en/interactive-modeQuick commands table says @ triggers file path autocomplete, but not that autocomplete works while entering slash-command arguments

Total scope: 3 pages affected

Source: Changelog v2.1.119

Exact changelog entry: Fixed @-file Tab completion replacing the entire prompt when used inside a slash command with an absolute path

Historical context: https://code.claude.com/docs/en/changelog already notes that v1.0.70 "Added support for @-mentions in slash command arguments", but that capability still does not appear to be documented on the main slash-command / file-reference pages.

extent analysis

TL;DR

Update the documentation for slash commands to explicitly mention that @ file references and their autocomplete work inside slash-command arguments.

Guidance

  • Add a note and example to the Pass arguments to skills section on the slash-commands page to clarify that skill arguments can include @ file references.
  • Include examples of using @ file references with relative and absolute paths in slash-command arguments.
  • Add a cross-reference from the file-reference guidance in common-workflows or interactive-mode to the updated Pass arguments to skills section.
  • Review the common-workflows and interactive-mode pages to ensure consistency in documenting @ file references and their usage in different contexts.

Example

> Skill arguments can include `@` file references, the same way regular prompts do.
> Examples:
> - `/explain-code @src/auth/login.ts`
> - `/explain-code @/absolute/path/to/src/auth/login.ts`

Notes

The suggested improvement should be applied to the affected pages, including https://code.claude.com/docs/en/slash-commands, https://code.claude.com/docs/en/common-workflows, and https://code.claude.com/docs/en/interactive-mode.

Recommendation

Apply the suggested workaround by updating the documentation to explicitly mention the support for @ file references in slash-command arguments, as this will improve the clarity and usability of the feature.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#inference speed#output truncation#response parsing#generation error#database connection

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING