remediate-failures

To fix QA failures and pass quality gates, you apply minimal, scope-preserving corrections to rule violations and acceptance criteria gaps. This iterative process detects issues, applies code adjustments, and re-validates until all quality gates pass.

Automating bug fixing after a QA review involves processing the failing QA report and associated artefacts to pinpoint exact failures. The system applies necessary code adjustments and resubmits for validation, looping until the story passes.

Iterative code remediation handles unresolved gaps by looping through detection, correction, and re-validation. If convergence is not achieved within three attempts or a fix requires redefining scope, it escalates the issue rather than forcing a resolution.

Yes, you can use automated remediation to correct rule violations identified during code review. It operates on failing QA reports and artefacts, producing updated code changes and remediation notes while ensuring fixes do not introduce new scope.

You should avoid using automated fixes when a failure requires redefining the original product scope. If the necessary corrections exceed minimal adjustments or cannot converge within three validation attempts, the process escalates instead of proceeding.

Yes, the remediate-failures skill operates without external dependencies. It processes failing QA reports and associated artefacts internally to apply minimal fixes, generate updated code changes, and produce remediation notes.