| name | validate-all |
| description | Runs comprehensive claudelint validation on all Claude Code project files. Use when user asks to "check everything", "run all validators", "full audit", "validate my entire project", or "what's wrong with my config". Validates CLAUDE.md, skills, settings, hooks, MCP servers, and plugin manifests. |
| version | 1.0.0 |
| argument-hint | [flags] |
| allowed-tools | ["Bash(claudelint:*)"] |
Validate Claude Code Project
Runs claudelint check-all to validate all Claude Code project files including CLAUDE.md, skills, settings, hooks, MCP servers, and plugin manifests.
Usage
claudelint check-all $ARGUMENTS
Options
Available flags:
--verbose - Show detailed validation output
--warnings-as-errors - Treat warnings as errors
--explain - Show detailed explanations and fix suggestions
--format <format> - Output format: stylish, json, compact (default: stylish)
--config <path> - Path to custom config file
--fast - Fast mode: skip expensive checks
--color / --no-color - Control color output
Examples
Example 1: Plugin won't load after changes
User says: "I just updated my CLAUDE.md and added a new skill, but now my plugin isn't loading"
What happens:
- Skill runs
claudelint check-all
- Finds CLAUDE.md exceeds 50KB (blocking issue)
- Finds new skill has wrong capitalization in allowed-tools
- Shows both issues need fixing before plugin will load
Result: User identifies why plugin broke and fixes both issues
Example 2: Pre-commit validation failed
User says: "My git pre-commit hook is failing but I don't know which validator is the problem"
What happens:
- Skill runs
claudelint check-all --verbose
- Shows validate-mcp failed: invalid transport type "sse" (deprecated)
- Shows validate-hooks passed, validate-skills passed, etc.
- Points to specific .mcp.json file and line number
Result: User fixes the one failing validator (MCP config) and commit succeeds
Example 3: After npm install, verify everything still works
User says: "I just upgraded claude-code-lint, make sure I didn't break anything"
What happens:
- Skill runs
claudelint check-all
- Detects new rules flagging previously-allowed patterns
- Shows deprecation warnings for old syntax
- Suggests migration path for deprecated features
Result: User knows what needs updating after version upgrade
Command Examples
Basic validation:
claudelint check-all
Verbose output with explanations:
claudelint check-all --verbose --explain
JSON output for CI/CD:
claudelint check-all --format json
Use custom config:
claudelint check-all --config .claudelintrc.custom.json
Treat warnings as errors (strict mode):
claudelint check-all --warnings-as-errors
What Gets Validated
The validate skill checks:
- CLAUDE.md files - File size, imports, frontmatter, sections
- Skills - SKILL.md schema, naming, documentation, security
- Settings - settings.json schema, permissions, environment variables
- Hooks - hooks.json schema, events, commands
- MCP Servers - .mcp.json schema, transport config, variables
- Plugins - plugin.json schema, semantic versioning, references
Exit Codes
0 - No errors or warnings
1 - Warnings found (or warnings treated as errors)
2 - Errors found or fatal error (invalid config, crash)
For troubleshooting, see common issues. For customization, see configuration.
See Also