From claude-code-project-analytics
Analyze project source files and display metrics (LOC, comments, coverage, complexity, file types)
How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-code-project-analytics:project-statsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Display comprehensive analytics for the current project including lines of code, comment density, test coverage, file type breakdown, and complexity metrics.
Display comprehensive analytics for the current project including lines of code, comment density, test coverage, file type breakdown, and complexity metrics.
When the user invokes this skill:
Step 1: Run the analyzer
Use Bash tool:
node "${CLAUDE_PLUGIN_ROOT}/src/analyzer.js" "${CLAUDE_PROJECT_DIR}"
Step 2: Display results
The analyzer outputs a formatted report to stdout. Present this directly to the user.
If the analyzer fails:
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub yuvalbetsalel/plugin_project --plugin claude-code-project-analytics