lmiranda
74b28170fa
- Remove Wiki.js MCP server entirely - Add wiki, milestone, and dependency tools to Gitea MCP server - Add parallel execution support based on dependency graph - Add mandatory pre-planning validations (org check, labels, docs/changes) - Add CLI blocking rules to all agents (API-only) - Add standardized task naming: [Sprint XX] <type>: <description> - Add branch naming convention: feat/, fix/, debug/ prefixes - Add MR body template without subtasks - Add auto-close issues via commit keywords - Create claude-config-maintainer plugin for CLAUDE.md optimization - Update all sprint commands with new tools and workflows - Update documentation to remove Wiki.js references New MCP tools: - Wiki: list_wiki_pages, get_wiki_page, create_wiki_page, create_lesson, search_lessons - Milestones: list_milestones, get_milestone, create_milestone, update_milestone - Dependencies: list_issue_dependencies, create_issue_dependency, get_execution_order - Validation: validate_repo_org, get_branch_protection, create_label 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 support-claude-mktplace collection. 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
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 bandit/support-claude-mktplace repository.