Help us improve
Share bugs, ideas, or general feedback.
From codebase-attributes-plugin
Renders compact terminal-style dashboard of codebase health scores, progress bars, severity breakdowns, and findings for quick visibility into documentation, testing, security, and more.
npx claudepluginhub laurigates/claude-plugins --plugin codebase-attributes-pluginHow this skill is triggered — by the user, by Claude, or both
Slash command
/codebase-attributes-plugin:attributes-dashboardhaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Compact text-based health dashboard with scores, bars, and findings.
Collects structured JSON attributes on codebase health for documentation, testing, security, code quality, and CI/CD with severity levels and remediation actions. Use for pre-agent assessment or repo comparisons.
Scores a project across PR quality, architecture, tech debt, and test quality in a single pass, drawing on twelve classic engineering books. Useful for big-picture codebase health assessments before releases or when onboarding a team.
Generates health scores for JS/TS projects assessing architecture conformance, test coverage, security risks, performance metrics, and maintainability. Use for onboarding, quality checks, or refactoring baselines.
Share bugs, ideas, or general feedback.
Compact text-based health dashboard with scores, bars, and findings.
| Use this skill when... | Use another approach when... |
|---|---|
| Want quick visual health overview | Need machine-readable JSON (use /attributes:collect) |
| Reviewing health before a session | Want to fix issues (use /attributes:route) |
| Comparing categories at a glance | Need detailed diagnostics (use /health:check) |
| Parameter | Description |
|---|---|
--format | Output format: compact (default), detailed |
Read .claude/attributes.json if it exists. Otherwise, perform the same checks as /attributes:collect inline.
Output a compact terminal-style dashboard:
Health: 72/100 (C) [██████████████░░░░░░]
Documentation 15/20 [███████████████░░░░░]
Testing 12/20 [████████████░░░░░░░░]
Security 8/20 [████████░░░░░░░░░░░░] 2 critical/high
Code Quality 17/20 [█████████████████░░░]
CI/CD 20/20 [████████████████████]
Critical: 2 High: 3 Medium: 5 Low: 8
⚠ Critical (2)
security: .env file committed to repository
security: No security scanning in CI
⚠ High (3)
tests: No test directory or test files found
tests: No CI workflow runs tests
security: Missing .gitignore
▲ Medium (5)
docs: Missing CLAUDE.md
...
If --format detailed, also show:
⚠ Critical (2)
security: .env file committed → agent:security "fix .env exposure" (manual)
security: No security scanning → agent:security "setup CI security scanning" [auto-fixable]
| Context | Command |
|---|---|
| Quick dashboard | /attributes:dashboard |
| Detailed with actions | /attributes:dashboard --format detailed |
| Check if data exists | test -f .claude/attributes.json && echo cached || echo fresh |