[DOCS] Documentation refers to non-existent SlashCommand tool - should reference Skill tool

Resolved 💬 2 comments Opened Jan 4, 2026 by PGrabinski Closed Jan 8, 2026

Preflight Checks

  • [x] I have searched for existing issues that might be duplicates
  • [x] I am filing a single issue
  • [x] I am on the latest version of Claude Code

Issue Type

Documentation

What's Wrong?

The slash commands documentation at https://code.claude.com/docs/en/slash-commands describes a "SlashCommand Tool" section that documents a tool called SlashCommand. However, this tool does not exist in the actual Claude Code toolset.

The actual tool available is named Skill, which has absorbed this functionality but with different semantics.

Documentation vs Reality

| Documented | Actual |
|------------|--------|
| Tool: SlashCommand | Tool: Skill |
| Permission: SlashCommand:/commit | Permission: Skill (syntax unclear) |
| Purpose: Execute custom slash commands | Purpose: "When users ask you to run a 'slash command'... they are referring to a skill" |

What Should Happen?

The documentation should be updated to:

  1. Correct the tool name - Reference Skill instead of SlashCommand (or clarify if both exist)
  2. Update permission syntax - Show current permission rule format
  3. Clarify the concepts - The current Skill tool description conflates slash commands with skills, which are documented as distinct features on the same page

Affected Documentation

Related Issues

This documentation gap is related to but distinct from these code behavior issues:

  • #14851 - Commands treated as skills without invocation (OPEN)
  • #11459 - Skills being interpreted as SlashCommands (OPEN)
  • #15017 - Skill tool description conflates slash commands with skills (CLOSED as duplicate)

Those issues address code behavior; this issue addresses documentation accuracy.

Environment

Additional Context

The current Skill tool description in the system prompt still contains text reported in closed issue #15017:

"When users ask you to run a 'slash command' or reference '/<something>' (e.g., '/commit', '/review-pr'), they are referring to a skill."

This suggests the underlying conflation hasn't been resolved, and the documentation has drifted from the actual implementation.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗