Repository navigation
Agent guidance: carry a ticket to a green PR — Ticket Delivery Loop, worktree hazards, scripts/pr-checks.sh - #183
Merged
Conversation
…worktree hazards, scripts/pr-checks.sh Adds a Ticket Delivery Loop section to AGENTS.md: an agent is finished when its PR has all four CI checks green, waits on CI with scripts/pr-checks.sh, fixes what it reports, and asks Miley through Conductor's question tool only when a person is needed. "Reading a red check" is built from a survey of the last 50 failed ci.yml runs. Also adds Git Worktree Hazards (Conductor), and reconciles Testing, Release, Safety Boundaries and Permissions with the loop. Authored by Claude (Opus 5.5), not by the committer. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No ticket, so no
Closes.Agents in Conductor workspaces were stopping at "PR opened, CI pending", or ending with a question buried in their closing message. This PR changes AGENTS.md so an agent carries its ticket to a PR with all four checks green. It waits on CI, fixes what CI reports, and asks Miley through Conductor's question tool only when a person is actually needed. It follows socket-link/socket#2007, adapted to this repo's facts.
Changes
scripts/pr-checks.sh(new, executable): waits on a PR's checks inside a budget that fits the Bash tool's 10-minute cap. Exit codes: 0 pass, 1 red, 2 no PR, 3 conflict, 8 still running.origin/main. Ifkotlin-js-store/or the generated agent docs conflict, takeorigin/main's and regenerate;.context/, and asks for a visual verdict once the PR is green;PHO-<n>/#<issue> <task>: …title shape with an authorship line.ghrights on the agent's own branch.The red-check table comes from a survey of the last 50 failed
ci.ymlruns.Couldn't resolve link(13) and the yarn lockfile (10, 8 of them inherited from a redmain).Deviations from the brief
mainis protected, by the "Protect Main" ruleset (13347139), which requires the four checks. The classic protection endpoint 404s, butgh pr checks --requiredreads the ruleset, so the script waits on exactly those four. The script's comment that says otherwise is left as given.--squash". This repo allows all three merge methods.Verification
bash -n scripts/pr-checks.shpasses.Ran the script read-only against these targets:
--fail-onNo Kotlin changes, so no Gradle run. CI is the check.
Authored by Claude (Opus 5.5), not by the committer.
🤖 Generated with Claude Code