What's clear: The document currently has no handling for when CI checks or local verification (pnpm check, pnpm typecheck, tests) fail on the merge request. Phase 7 covers review comments but not check failures. The agent should detect failing checks, investigate, fix, and push.

Scope: Add error handling for failing checks in Phase 7, and potentially a new Error Handling subsection for CI failures.

No clarifying questions — the intent is clear. Proceeding to planning.

## Triage Assessment **What's clear:** The document currently has no handling for when CI checks or local verification (`pnpm check`, `pnpm typecheck`, tests) fail on the merge request. Phase 7 covers review comments but not check failures. The agent should detect failing checks, investigate, fix, and push. **Scope:** Add error handling for failing checks in Phase 7, and potentially a new Error Handling subsection for CI failures. **No clarifying questions** — the intent is clear. Proceeding to planning.

ReadyPlayerNaN added the

planning

label

2026-03-19 11:18:44 +00:00

ReadyPlayerNaN commented

2026-03-19 11:18:57 +00:00

Author

Owner

Plan

Goal: Add error handling for failing CI checks and local verification so the agent knows how to respond when checks don't pass on a merge request.

Approach: Add instructions to Phase 7 for detecting and responding to check failures, and add a new Error Handling subsection for persistent check failures.

Tasks:

Phase 7 — add check failure handling. After the existing review comment handling (step 2), add a step for monitoring CI/check status on the MR. When checks fail:
- Read the check output / CI logs.
- Identify the failing check (lint, typecheck, tests, etc.).
- Fix the issue locally, commit, and push.
- Re-run local verification (pnpm check, pnpm typecheck, tests) before pushing.
Error Handling — add "Checks Failing" subsection. If checks fail repeatedly and the agent cannot fix them after a reasonable effort:
- Comment on the MR describing the failure and what was attempted.
- Comment on the original issue.
- Follow the existing "Agent Is Stuck" pattern.

Risks:

The specific method to read CI logs varies by platform. The doc should state the principle (read logs, fix, push) without prescribing a single API.

Test strategy:

Read the updated Phase 7 to verify it covers both review comments and check failures.
Verify the new error handling subsection is consistent with existing error handling patterns.

## Plan **Goal:** Add error handling for failing CI checks and local verification so the agent knows how to respond when checks don't pass on a merge request. **Approach:** Add instructions to Phase 7 for detecting and responding to check failures, and add a new Error Handling subsection for persistent check failures. **Tasks:** 1. **Phase 7 — add check failure handling.** After the existing review comment handling (step 2), add a step for monitoring CI/check status on the MR. When checks fail: - Read the check output / CI logs. - Identify the failing check (lint, typecheck, tests, etc.). - Fix the issue locally, commit, and push. - Re-run local verification (`pnpm check`, `pnpm typecheck`, tests) before pushing. 2. **Error Handling — add "Checks Failing" subsection.** If checks fail repeatedly and the agent cannot fix them after a reasonable effort: - Comment on the MR describing the failure and what was attempted. - Comment on the original issue. - Follow the existing "Agent Is Stuck" pattern. **Risks:** - The specific method to read CI logs varies by platform. The doc should state the principle (read logs, fix, push) without prescribing a single API. **Test strategy:** - Read the updated Phase 7 to verify it covers both review comments and check failures. - Verify the new error handling subsection is consistent with existing error handling patterns.

👍 1

ReadyPlayerNaN added

implementing

and removed

planning

labels

2026-03-19 11:19:10 +00:00

ReadyPlayerNaN referenced this issue from a commit

2026-03-19 11:21:23 +00:00

docs: add handling for failing CI checks in Phase 7

ReadyPlayerNaN referenced this issue from a pull request that will close it,

2026-03-19 11:21:29 +00:00