Failing GitHub Actions
Suitable when the scope and expected result can be made explicit before implementation.
CI Rescue
Get the pipeline back to a state your team can trust.
We reproduce the failing checks, separate baseline problems from the current blocker, repair the exact CI path, rerun the evidence, and hand back a reviewed pull request.
Good fit
Bounded work with a visible finish line.
Flaky tests
Suitable when the scope and expected result can be made explicit before implementation.
Lint / type-check failures
Suitable when the scope and expected result can be made explicit before implementation.
Broken build or packaging steps
Suitable when the scope and expected result can be made explicit before implementation.
Read-only preflight
What we verify first.
Preflight gathers evidence. It does not authorize implementation.
Exact failing workflow/check
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Recent run evidence
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Build/test commands
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Environment assumptions and required secrets boundaries
Captured as evidence for qualification and the Sprint Brief before implementation begins.
Lane use
Implementation stays inside the approved brief.
The lane receives the exact failing checks and approved repair scope. It may fix configuration or code only as required to restore the agreed pipeline behavior; unrelated cleanup stays out of scope.
Definition of done
Evidence before handoff.
The named checks pass or have a documented external blocker, baseline failures are separated, and the repair is independently reviewed.
Client controls merge. Deploy remains off by default.