Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.7 KiB
2.7 KiB
CLAUDE.md Maintenance (claude-config-maintainer)
This project uses the claude-config-maintainer plugin to analyze and optimize CLAUDE.md and settings.local.json configuration files.
Available Commands
| Command | Description |
|---|---|
/claude-config analyze |
Analyze CLAUDE.md for optimization opportunities with 100-point scoring |
/claude-config optimize |
Automatically optimize CLAUDE.md structure and content |
/claude-config init |
Initialize a new CLAUDE.md file for a project |
/claude-config diff |
Track CLAUDE.md changes over time with behavioral impact analysis |
/claude-config lint |
Lint CLAUDE.md for anti-patterns and best practices (31 rules) |
/claude-config audit-settings |
Audit settings.local.json permissions with 100-point scoring |
/claude-config optimize-settings |
Optimize permission patterns and apply named profiles |
/claude-config permissions-map |
Visual map of review layers and permission coverage |
CLAUDE.md Scoring System
The analysis uses a 100-point scoring system across four categories:
| Category | Points | What It Measures |
|---|---|---|
| Structure | 25 | Organization, headers, navigation, grouping |
| Clarity | 25 | Instructions, examples, language, detail level |
| Completeness | 25 | Overview, quick start, critical rules, workflows |
| Conciseness | 25 | Efficiency, no repetition, appropriate length |
Settings Scoring System
The settings audit uses a 100-point scoring system across four categories:
| Category | Points | What It Measures |
|---|---|---|
| Redundancy | 25 | No duplicates, no subset patterns, efficient rules |
| Coverage | 25 | Common tools allowed, MCP servers covered |
| Safety Alignment | 25 | Deny rules for secrets/destructive ops, review layers verified |
| Profile Fit | 25 | Alignment with recommended profile for review layer count |
Permission Profiles
| Profile | Use Case |
|---|---|
conservative |
New users, minimal auto-allow, prompts for most writes |
reviewed |
Projects with 2+ review layers (code-sentinel, doc-guardian, PR review) |
autonomous |
Trusted CI/sandboxed environments only |
Usage Guidelines
- Run
/claude-config analyzeperiodically to assess CLAUDE.md quality - Run
/claude-config audit-settingsto check permission efficiency - Target a score of 70+/100 for effective Claude Code operation
- Address HIGH priority issues first when optimizing
- Use
/claude-config initwhen setting up new projects to start with best practices - Use
/claude-config permissions-mapto visualize review layer coverage - Re-analyze after making changes to verify improvements