From devac
Guide Claude through efficiently fixing validation errors detected by DevAC.
How this skill is triggered — by the user, by Claude, or both
Slash command
/devac:diagnostics-fixThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guide Claude through efficiently fixing validation errors detected by DevAC.
Guide Claude through efficiently fixing validation errors detected by DevAC.
This skill activates when users ask:
Understand what's broken and why by querying diagnostic details.
Determine optimal fix order based on error types and dependencies.
Group related errors for efficient resolution.
Confirm fixes resolved the issues before moving on.
Use CLI for lower context overhead:
devac status --diagnostics --json
Or via MCP tool:
status_all_diagnostics(level: "details", severity: ["error"])
Group errors by:
After fixing a batch, run quick validation:
devac validate --mode quick
Or wait for the Stop hook to validate automatically after your edits.
Repeat steps 1-4 until devac status --diagnostics shows no errors.
The Stop hook runs after code changes and may report validation issues:
Validation found issues:
- 2 TypeScript errors in src/foo.ts
- 1 ESLint warning in src/bar.ts
When this happens:
<system-reminder> for file locationsAt the start of conversations, you may see:
DevAC Status: 5 errors, 12 warnings
Use status_all_diagnostics MCP tool to see details.
When this happens:
status_all_diagnostics to get full detailsUser: "Fix the errors"
Response approach:
devac status --diagnostics --jsonUser: "There are TypeScript errors in the auth module"
Response approach:
devac status --diagnostics --file src/auth/devac validate --mode quicknpx claudepluginhub pietgk/vivief --plugin devacDiagnoses and fixes TypeScript compile errors, runtime exceptions, build failures, and test issues in JavaScript/Node.js projects via linting, dependency reinstalls, and code patterns. Use for task failures.
Runs existing project validation (lint, type-check, test, build) and fixes failures after code changes, following a structured triage and repair process.
Diagnoses and fixes test failures, build errors, runtime errors, environment issues, and more by categorizing errors and applying targeted strategies with minimal context.