Stats
Actions
Tags
From devac
Triages and prioritizes diagnostics, errors, and issues from DevAC validators using CLI commands like devac status --diagnostics. Handles TypeScript errors, ESLint warnings, and test failures across workspaces.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devac:diagnostics-triageThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Triage and prioritize diagnostics, errors, and issues using DevAC's Validators Pillar outputs.
Triage and prioritize diagnostics, errors, and issues using DevAC's Validators Pillar outputs.
DevAC automatically injects diagnostic status into Claude Code conversations via hooks:
When you start a conversation, if there are unresolved errors or warnings, DevAC automatically injects a status reminder:
DevAC Status: 3 errors, 2 warnings
Run get_all_diagnostics to see details.
After code changes are made, the Stop hook runs quick validation and reminds you of any new issues introduced:
Validation found issues:
- 2 TypeScript errors in src/foo.ts
- 1 ESLint warning in src/bar.ts
Consider fixing these before continuing.
The hooks enable an iterative workflow:
This creates a natural loop that keeps the codebase healthy.
To disable automatic injection, remove or comment out entries in plugins/devac/hooks/hooks.json.
This skill activates when users ask about:
Get a high-level summary of all issues across the workspace.
Intelligently prioritize which issues to fix first based on severity and impact.
Understand the distribution of issues by type (TypeScript, ESLint, test failures).
See diagnostics across all connected repositories in hub mode.
Use DevAC CLI commands for diagnostics. CLI is preferred for lower context overhead.
devac status --diagnosticsGet diagnostics overview across the workspace.
devac status --diagnostics
devac status --diagnostics --severity error
devac status --diagnostics --file src/services/
devac sync --validateRun validators and refresh diagnostics.
devac sync --validate
devac sync --validate --type typescript
devac sync --validate --type eslint
devac queryAdvanced diagnostic queries.
devac query "SELECT file_path, COUNT(*) as error_count FROM diagnostics WHERE severity = 'error' GROUP BY file_path ORDER BY error_count DESC LIMIT 10"
User: "What needs fixing in the codebase?"
Response approach:
devac status --diagnostics for overviewUser: "Show me all TypeScript errors"
Response approach:
devac status --diagnostics --severity error filtered by typeUser: "Which files have the most issues?"
Response approach:
devac query to aggregate diagnostics by fileWhen many similar issues exist:
If MCP server is configured, these tools provide equivalent functionality:
get_all_diagnosticsSupports progressive disclosure via the level parameter:
# Fast: just get counts
get_all_diagnostics(level: "counts")
# Returns: { critical: 0, error: 3, warning: 2, suggestion: 0, note: 0, total: 5 }
# Medium: get summary grouped by source
get_all_diagnostics(level: "summary")
# Returns: [{ source: "tsc", count: 2 }, { source: "eslint", count: 3 }]
# Full: get all diagnostic records (default)
get_all_diagnostics(level: "details", severity: ["error"])
# Returns: full diagnostic records with file paths, messages, etc.
get_diagnostics_summaryget_diagnostics_summary(groupBy: "source")
get_diagnostics_countsget_diagnostics_counts()
query_sqlSELECT file_path, COUNT(*) as error_count
FROM diagnostics
WHERE severity = 'error'
GROUP BY file_path
ORDER BY error_count DESC
LIMIT 10
devac sync --validate to update diagnosticsnpx claudepluginhub pietgk/vivief --plugin devacRuns modular quality probes adapted to the project's tech stack. Discovers issues via /discovery or session-end, then creates VCS tickets for confirmed problems.
Runs a structured 14-dimension bug hunt using Draft context (architecture, tech-stack, product) to eliminate false positives. Generates severity-ranked reports with code evidence, data flow traces, and optional regression tests.
Performs repo-wide or PR diff readiness sweeps dispatching parallel agents across security (shieldkit), tests (testkit), codebase (lenskit), evolution (timewarp), and instructions (alignkit) for synthesized reports.