Guides
Use a coding agent to find and fix quality debt
Survey tests, code, accessibility, contracts, docs, dependencies, and security, then work only applicable findings.
Answers: use a coding agent to fix quality debt · Updated
Use the Quality workflow to inspect the project across quality categories, deduplicate findings, and either fix selected debt now, draft it for later, or consciously ignore it with a reason.
What Quality surveys
The scan follows the project’s actual stack and risk surface rather than imposing every possible tool.
- Tests and coverage gaps
- Code correctness and maintainability
- Accessibility
- API and data contracts
- Documentation drift
- Dependencies and security
Choose the execution mode
Guided mode lets the owner select categories. Automatic mode ranks applicable work. Review-first arms nothing; run-direct is explicit authority to start immediately.
- Fix now for bounded, approved debt.
- Draft when the finding is useful but not authorized.
- Ignore only with a recorded reason.
Converge instead of looping
Every review cycle checks the snag log so fixed or rejected findings are not rediscovered. A full pass with nothing new is success.
Start with a bounded prompt
This prompt names the outcome and preserves Nightshift’s review boundary. Paste it into the supported coding host from the project you want to change.
Survey this project's applicable quality debt. Show me lint, types, tests, accessibility, contracts, documentation, dependencies, and security findings before I choose what to fix.What this workflow does not claim
- Review-first discovery writes no fixes and must be explicitly promoted or run directly.
- A finding may be ignored or parked when it is inapplicable or requires an owner decision.
Evidence and sources
These links support the released behavior, public outcomes, or problem language described on this page.