lmiranda
5bbcee06ac
All dispatch files referenced display names (e.g., `/doc audit`) that don't correspond to real slash commands. Claude Code resolves commands by filename, so `/doc audit` loads `doc.md` with $ARGUMENTS but never routes to `doc-audit.md`. Changes: - Updated 24 dispatch files with explicit Skill tool routing - Added "Command to Invoke" column with plugin-prefixed names - Added $ARGUMENTS matching for automatic routing - RFC dispatch file uses inline handling (no separate command files) - Updated COMMANDS-CHEATSHEET.md with invocation methods - Updated MIGRATION-v9.md with command name mapping explanation Affects: 25 dispatch files across 12 plugins (core, data, saas, ops, debug) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
name, description
| name | description |
|---|---|
| claude-config | CLAUDE.md and settings optimization — type /claude-config <action> for commands |
/claude-config
CLAUDE.md and settings.local.json optimization for Claude Code projects.
When invoked without a sub-command, display available actions and ask which to run.
Available Commands
| Action | Command to Invoke | Description |
|---|---|---|
analyze |
/claude-config-maintainer:claude-config-analyze |
Analyze CLAUDE.md for optimization opportunities |
optimize |
/claude-config-maintainer:claude-config-optimize |
Optimize CLAUDE.md structure with preview/backup |
init |
/claude-config-maintainer:claude-config-init |
Initialize new CLAUDE.md for a project |
diff |
/claude-config-maintainer:claude-config-diff |
Track CLAUDE.md changes over time with behavioral impact |
lint |
/claude-config-maintainer:claude-config-lint |
Lint CLAUDE.md for anti-patterns and best practices |
audit-settings |
/claude-config-maintainer:claude-config-audit-settings |
Audit settings.local.json permissions (100-point score) |
optimize-settings |
/claude-config-maintainer:claude-config-optimize-settings |
Optimize permissions (profiles, consolidation, dry-run) |
permissions-map |
/claude-config-maintainer:claude-config-permissions-map |
Visual review layer + permission coverage map |
Routing
If $ARGUMENTS is provided (e.g., user typed /claude-config analyze):
- Match the first word of
$ARGUMENTSagainst the Action column above - Invoke the corresponding command from the "Command to Invoke" column using the Skill tool
- Pass any remaining arguments to the invoked command
If no arguments provided:
- Display the Available Commands table
- Ask: "Which action would you like to run?"
- When the user responds, invoke the matching command using the Skill tool
Note: Commands can also be invoked directly using their plugin-prefixed names (e.g., /claude-config-maintainer:claude-config-analyze)