fix(skills/developing-a-feature): proceed with teardown when the repo has no CI#11
Merged
Conversation
… has no CI Step 7 gated teardown of the plan/state files on the integration PR's CI going green, with no branch for repos that run no CI. A faithful agent then polls for checks that never appear and stalls. The text also gave no way to tell "no CI exists" from "CI hasn't registered yet," so the agent couldn't safely conclude either. Key the gate on inspecting the repo's CI configuration instead of polling run state: if a pipeline is wired to run on the PR's branch, wait for green as before; if none is, the full local suite already pasted via verification-before-completion is the authority, so proceed. Refine the "local green isn't the gate" red flag to scope it to "when CI runs," and add a red flag against polling for checks that will never appear. Co-Authored-By: Claude Opus 4.8 (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.
Description
The teardown step (
developing-a-featureStep 7) gated deleting the plan/statefiles on the integration PR's CI going green, but had no branch for repositories
that run no CI. An agent following it faithfully polls for checks that never
appear and stalls — the workflow hangs at the finish line. The text also gave no
way to distinguish "no CI exists" from "CI hasn't registered yet," so the agent
couldn't safely conclude either. This keys the gate on the repo's CI
configuration instead, so the workflow completes whether or not CI is present.
Changes
not by polling
gh pr checksrun state (which can't tell absent from pending).verification-before-completionis the authority, so proceed; no polling.red flag against polling for checks that will never appear.
Testing
Developed through
superpowers:writing-skillsRED → GREEN → REFACTOR withisolated subagents:
status unknown), refused to count local green, fell back to arbitrary
time-based polling, and stalled — reproducing the reported hang.
configuration and tears down immediately, no polling.
agent still waits for green and refuses premature teardown. No hole opened.
JSON in
.claude-plugin/unaffected; no provider- or product-specific stringsintroduced (the skill says "inspect the repo's CI configuration").
🤖 Generated with Claude Code