[DOCS] [Commands] `/context` output docs omit plugin names for plugin-sourced skills
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/commands
Section/Topic
The /context entry in the Commands reference
Current Documentation
The docs currently describe /context as:
"Visualize current context usage as a colored grid. Shows optimization suggestions for context-heavy tools, memory bloat, and capacity warnings"
This description does not mention that the output groups skills and agents by source, or that plugin-sourced skills display the providing plugin's name in the visualization.
What's Wrong or Missing?
A. Missing description of skill grouping by source
The /context visualization now groups skills and agents by source (user, project, plugin), but the documentation does not describe this grouping behavior.
B. Missing plugin-name display for plugin-sourced skills
When plugin-sourced skills appear in the /context output, the visualization now shows the providing plugin's name alongside the skill name. This helps users identify which plugin provides a given skill when they have many skills installed. The current documentation does not mention this.
Suggested Improvement
Update the /context entry in commands.md to reflect the current behavior:
After:
/context — Visualize current context usage as a colored grid. Shows optimization suggestions for context-heavy tools, memory bloat, and capacity warnings. Skills and agents are grouped by source (user, project, plugin), and plugin-sourced skills show the providing plugin's name.
Impact
Medium - Makes feature difficult to understand
Additional Context
Changelog reference (v2.1.139):
Improved /context command visualization with grouped skills and agents by source, slash commands, and sorted token count
Affected Pages:
| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/commands | /context command description (Section 3 above) |
Total scope: 1 page affected
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗