Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Allow skills to disable or customize @-mention autocomplete in arguments [2 comments, 2 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#47938•Fetched 2026-04-15 06:38:03
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
drudolfdrudolf
Participants
drudolfdrudolfgithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×2closed ×1

Fix Action

Fix / Workaround

A skill that dispatches work to named roles via @mentions in the arguments:

Code Example

/my-skill review the auth module @security @backend

---

completions:
  "@": [alice, bob, backend, frontend, security]
RAW_BUFFERClick to expand / collapse

Preflight Checklist

What Would You Like?

When typing arguments for a custom skill (e.g. /my-skill @), the @ character triggers the built-in file/folder autocomplete. This is unhelpful when the skill uses @ for its own domain-specific mentions (e.g. @alice, @backend-team).

Requested: A way for skills to control @-autocomplete behavior in their arguments. Either:

  1. A frontmatter option to disable @-autocomplete for a skill (disable-autocomplete: true or autocomplete: false)
  2. A way to define custom completions per skill, so @ suggests skill-defined values instead of files

Use Case

A skill that dispatches work to named roles via @mentions in the arguments:

/my-skill review the auth module @security @backend

Typing @ shows pnpm-lock.yaml, node_modules/, .claude/, etc. — none of which are valid for this skill. The file suggestions clutter the input and cause typos when accidentally accepted.

Proposed Solution

Option 1 (minimal): Add a disable-autocomplete: true frontmatter key that suppresses the built-in @-file autocomplete for that skill's arguments.

Option 2 (richer): Allow skills to define custom completions in frontmatter, e.g.:

completions:
  "@": [alice, bob, backend, frontend, security]

Claude Code Version

Latest

Platform

macOS

extent analysis

TL;DR

Implement a frontmatter option to control @-autocomplete behavior for custom skills, either by disabling it or defining custom completions.

Guidance

  • Consider adding a disable-autocomplete: true frontmatter key to suppress the built-in @-file autocomplete for specific skills.
  • Alternatively, explore defining custom completions in frontmatter using a completions key, mapping the @ character to a list of skill-defined values.
  • Verify the proposed solution by testing it with the provided use case, ensuring that typing @ suggests the expected values instead of file names.
  • Evaluate the trade-offs between the minimal (Option 1) and richer (Option 2) solutions, considering factors like implementation complexity and user experience.

Example

# Minimal solution (Option 1)
disable-autocomplete: true

# Richer solution (Option 2)
completions:
  "@": [alice, bob, backend, frontend, security]

Notes

The proposed solution assumes that the Claude Code platform supports custom frontmatter keys and values. If this is not the case, alternative approaches may be necessary.

Recommendation

Apply the minimal workaround (Option 1: disable-autocomplete: true) as a temporary solution, allowing skills to opt-out of the built-in @-autocomplete behavior while a more comprehensive solution is developed.

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…
#chain error#conversation history#tool integration#LLM response#prompt template

Still need to ship something?

×6

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

Back to top recommendations

TRENDING