Skip to content

agents(monitor-ci-results): autonomous flake retries via subagent and forbid file lists in PRs #4001

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rickeylev merged 1 commit into from
Aug 5, 2026
+16 −2
Merged

agents(monitor-ci-results): autonomous flake retries via subagent and forbid file lists in PRs #4001

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 13 additions & 2 deletions .agents/skills/monitor-ci-results/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,10 @@ or when monitoring CI after PR updates:
> launch duplicate monitoring jobs for the same PR.

1. **Check Existing Process**: Check if a monitor script is already running for
the PR (e.g., `pgrep -f "monitor_remote_ci.py <pr_number>"`). If one is
already running, do not start another instance.
**this specific PR** using `pgrep -f "monitor_remote_ci.py <pr_number>"`. Do
NOT use a generic grep without `<pr_number>`, as other active agent
conversations may be monitoring different PRs concurrently. If one is
already running for this PR, do not start another instance.
2. **Launch Monitoring Script**: If no monitor process is active for
`<pr_number>`, launch the script in the background:
```bash
Expand All @@ -35,3 +37,12 @@ or when monitoring CI after PR updates:
the monitoring script, immediately launch a separate subagent using the
`invoke_subagent` tool with the role "CI Failure Analyzer" to run the
`analyze-ci-failure` skill on the reported failure.
5. **Autonomous Flake Retry**: If the CI Failure Analyzer subagent confirms
that the failure is a transient infrastructure or network flake (e.g. disk
I/O error, 504 gateway, sandbox initialization failure), **immediately and
autonomously** launch a separate subagent using `invoke_subagent` with the
role "CI Job Retrier" and the prompt template in
`.agents/skills/monitor-ci-results/retry-job-prompt.md` to run the
`buildkite-retry-job` skill for `<pr_number>`. Do not execute the script
directly; use the subagent and skill orchestration instead. Continue
monitoring without pausing to ask the user.
3 changes: 3 additions & 0 deletions .agents/skills/monitor-ci-results/retry-job-prompt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
Use the `buildkite-retry-job` skill to retry the failed Buildkite job(s) for PR {pr_number}.
Follow the instructions in `.agents/skills/buildkite-retry-job/SKILL.md` to retry the failing jobs using the skill.
Once the retry request completes, report back to the parent conversation.