Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From codebase-attributes-plugin
Routes to specialized agents like security-audit and test_runner to automatically remediate codebase health findings prioritized by severity after /attributes:collect. Use --dry-run to preview.
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-routesonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Route to specialized agents based on codebase health attributes.
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.
Assesses codebase for AI agent readiness by detecting stacks, monorepos, git setup, and evaluating style, testing, code quality, secrets, and file sizes.
Runs codebase audits (health, evaluation, documentation) with parallel agents, producing intake docs for a pipeline run.
Share bugs, ideas, or general feedback.
Route to specialized agents based on codebase health attributes.
| Use this skill when... | Use another approach when... |
|---|---|
| Have attribute data and want automated remediation | Need to collect attributes first (use /attributes:collect) |
| Want severity-based agent prioritization | Know exactly which agent to use |
| Batch-fixing multiple health findings | Fixing a single specific issue |
| Parameter | Description |
|---|---|
--dry-run | Show routing plan without spawning agents |
--focus <category> | Only route for: docs, tests, security, quality, ci |
--min-severity <level> | Minimum severity: critical, high, medium (default), low |
Read attribute data from one of:
.claude/attributes.json (if exists)/attributes:collect to generate fresh data--focus category if specified--min-severity thresholdactions arrayShow the routing plan:
Attribute-Based Routing
Based on attribute analysis, prioritize these agents in order:
1. security (priority 7): .env file committed; No security scanning in CI
2. test_runner (priority 3): No test directory or test files found
3. docs (priority 2): Missing CLAUDE.md
If --dry-run, stop here.
For each agent in priority order, spawn the agent with its findings as context:
| Attribute Category | Agent | Condition |
|---|---|---|
| security (critical/high) | security-audit | Always route first |
| tests | test | When test gaps found |
| quality (high+) | refactor | Anti-patterns exceed threshold |
| quality (medium) | review | Code review suggestions |
| docs | docs | Documentation gaps |
| ci | configure | CI configuration gaps |
When spawning each agent, include:
After all agents complete, summarize:
| Context | Command |
|---|---|
| Preview routing | /attributes:route --dry-run |
| Security only | /attributes:route --focus security |
| Critical only | /attributes:route --min-severity critical |
| Full remediation | /attributes:route |