Refactored commands to extract reusable skills following the Commands → Skills separation pattern. Each command is now <50 lines and references skill files for detailed knowledge. Plugins refactored: - claude-config-maintainer: 5 commands → 7 skills - code-sentinel: 3 commands → 2 skills - contract-validator: 5 commands → 6 skills - data-platform: 10 commands → 6 skills - doc-guardian: 5 commands → 6 skills (replaced nested dir) - git-flow: 8 commands → 7 skills Skills contain: workflows, validation rules, conventions, reference data, tool documentation Commands now contain: YAML frontmatter, agent assignment, skills list, brief workflow steps, parameters Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.7 KiB
2.7 KiB
CLAUDE.md Analysis Workflow
This skill defines the workflow for analyzing CLAUDE.md files.
Analysis Steps
- Locate File - Find CLAUDE.md in project root
- Parse Structure - Extract headers and sections
- Evaluate Content - Score against criteria
- Detect Plugins - Identify active marketplace plugins
- Check Integration - Verify plugin references
- Generate Report - Provide scored assessment
Content Analysis
What to Check
| Area | Check For |
|---|---|
| Structure | Header hierarchy, section ordering, grouping |
| Clarity | Clear instructions, examples, unambiguous language |
| Completeness | Required sections present, workflows documented |
| Conciseness | No redundancy, efficient density, appropriate length |
Required Sections Check
- Project Overview - present?
- Quick Start - present with commands?
- Critical Rules - present?
- Pre-Change Protocol - present? (HIGH PRIORITY if missing)
Plugin Integration Analysis
Detection Method
- Read
.claude/settings.local.jsonfor enabled MCP servers - Map MCP servers to plugins:
gitea-> projmannetbox-> cmdb-assistant
- Check for hook-based plugins (project-hygiene)
- Scan CLAUDE.md for plugin references
Coverage Scoring
For each detected plugin, verify CLAUDE.md contains:
- Plugin section header or mention
- Available commands documentation
- MCP tools reference (if applicable)
- Usage guidelines
Coverage = (plugins referenced / plugins detected) * 100%
Report Format
CLAUDE.md Analysis Report
=========================
File: /path/to/project/CLAUDE.md
Lines: N
Last Modified: YYYY-MM-DD
Overall Score: NN/100
Category Scores:
- Structure: NN/25 (Rating)
- Clarity: NN/25 (Rating)
- Completeness: NN/25 (Rating)
- Conciseness: NN/25 (Rating)
Strengths:
+ [Positive finding]
Issues Found:
N. [SEVERITY] Issue description (location)
Context explaining the problem.
Impact: What happens if not fixed.
Recommendations:
N. Action to take (priority: high/medium/low)
---
Plugin Integration Analysis
===========================
Detected Active Plugins:
[check] plugin-name (via detection method)
Plugin Coverage: NN% (N/N plugins referenced)
Missing Integration Content:
N. plugin-name
What to add.
Issue Severity
| Level | When to Use |
|---|---|
| HIGH | Missing mandatory sections, security issues |
| MEDIUM | Missing recommended content, duplicate content |
| LOW | Formatting issues, minor improvements |
Follow-Up Actions
After analysis, offer:
- Implement all content recommendations
- Add missing plugin integrations
- Do both (recommended)
- Show preview of changes first