lmiranda
2d51df7a42
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>
1.1 KiB
1.1 KiB
name, description
| name | description |
|---|---|
| claude-config lint | Lint CLAUDE.md for common anti-patterns and best practices |
/claude-config lint
Check CLAUDE.md against best practices and detect common anti-patterns.
Skills to Load
- skills/visual-header.md
- skills/lint-rules.md
Visual Output
Display: CONFIG-MAINTAINER - CLAUDE.md Lint
Usage
/claude-config lint # Full lint
/claude-config lint --fix # Auto-fix issues
/claude-config lint --rules=security # Check specific category
Workflow
- Parse markdown structure and hierarchy
- Check for hardcoded paths, secrets, sensitive data
- Identify content anti-patterns
- Verify consistent formatting
- Generate report with fix suggestions
Options
| Option | Description |
|---|---|
--fix |
Auto-fix issues |
--rules=LIST |
Check specific categories |
--ignore=LIST |
Skip specified rules |
--severity=LEVEL |
Filter by severity |
--strict |
Treat warnings as errors |
When to Use
- Before committing CLAUDE.md changes
- During code review
- Periodically as maintenance