lmiranda
9550a85f4d
BREAKING: Removes automatic venv management that was causing session failures Changes: - Delete scripts/venv-repair.sh (was deleting and recreating venvs) - Remove auto-repair code from projman/hooks/startup-check.sh - Remove venv-repair call from scripts/post-update.sh - Remove rm -rf .venv instructions from docs/UPDATING.md and CONFIGURATION.md - Update docs/CANONICAL-PATHS.md to remove venv-repair.sh reference Additionally: - Add Pre-Change Protocol to CLAUDE.md (mandatory dependency check before edits) - Add Pre-Change Protocol enforcement to claude-config-maintainer plugin - Add Development Context section to CLAUDE.md clarifying which plugins are used in this project vs only being developed - Reorganize commands table to separate relevant vs non-relevant commands The venv auto-repair was the root cause of repeated MCP server failures, requiring manual setup.sh runs after every session start. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Claude Config Maintainer
A Claude Code plugin for creating and maintaining optimized CLAUDE.md configuration files.
Overview
CLAUDE.md files provide instructions to Claude Code when working with a project. This plugin helps you:
- Analyze existing CLAUDE.md files for improvement opportunities
- Optimize structure, clarity, and conciseness
- Initialize new CLAUDE.md files with project-specific content
Installation
This plugin is part of the Leo Claude Marketplace. Install the marketplace and the plugin will be available.
Commands
/config-analyze
Analyze your CLAUDE.md and get a detailed report with scores and recommendations.
/config-analyze
/config-optimize
Automatically optimize your CLAUDE.md based on best practices.
/config-optimize
/config-init
Create a new CLAUDE.md tailored to your project.
/config-init
/config-diff
Show differences between current CLAUDE.md and previous versions.
/config-diff # Compare working copy vs last commit
/config-diff --commit=abc1234 # Compare against specific commit
/config-diff --from=v1.0 --to=v2.0 # Compare two commits
/config-diff --section="Critical Rules" # Focus on specific section
/config-lint
Lint CLAUDE.md for common anti-patterns and best practices.
/config-lint # Run all lint checks
/config-lint --fix # Auto-fix fixable issues
/config-lint --rules=security # Check only security rules
/config-lint --severity=error # Show only errors
Lint Rule Categories:
- Security (SEC) - Hardcoded secrets, paths, credentials
- Structure (STR) - Header hierarchy, required sections
- Content (CNT) - Contradictions, duplicates, vague rules
- Format (FMT) - Consistency, code blocks, whitespace
- Best Practice (BPR) - Missing Quick Start, Critical Rules sections
Best Practices
A good CLAUDE.md should be:
- Clear - Easy to understand at a glance
- Concise - No unnecessary content
- Complete - All essential information included
- Current - Up to date with the project
Recommended Structure
# CLAUDE.md
## Project Overview
What does this project do?
## Quick Start
Essential build/test/run commands.
## Critical Rules
What must Claude NEVER do?
## Architecture (optional)
Key technical decisions.
## Common Operations (optional)
Frequent tasks and workflows.
Length Guidelines
| Project Size | Recommended Lines |
|---|---|
| Small | 50-100 |
| Medium | 100-200 |
| Large | 200-400 |
Scoring System
The analyzer scores CLAUDE.md files on:
- Structure (25 pts) - Organization and navigation
- Clarity (25 pts) - Clear, unambiguous instructions
- Completeness (25 pts) - Essential sections present
- Conciseness (25 pts) - Efficient information density
Target score: 70+ for effective Claude Code usage.
Tips
- Run
/config-analyzeperiodically to maintain quality - Update CLAUDE.md when adding major features
- Keep critical rules prominent and clear
- Include examples where they add clarity
- Remove generic advice that applies to all projects
Contributing
This plugin is part of the personal-projects/leo-claude-mktplace repository.