gh CLI with push access, and a supported coding agent.
Use a local checkout of a GitHub repository. Review also needs required CI
checks on its default branch.
1
Prepare your repository
From the local checkout, run:Read the preview and approve the changes. Setup installs the five skills,
prepares labels, and checks readiness. It can require an existing successful
CI check when your permissions and GitHub plan support rulesets.If you have not created a repository yet, you can first run
npx @opengsd/gsd-loop@latest install. See installation.2
Specify a clear idea
Start a new agent session in your project and invoke Describe who needs the change, what they should be able to do, and what is
out of scope. Answer the interview questions and review the proposed issue.
For an uncertain effort, start with
gsd-loop-spec using
your host’s syntax. In Codex:gsd-loop-discover instead.3
Approve each issue
Read the filed GitHub issue. Check its
O-N outcomes and X-N exclusions.
Add gsd:ready to each issue you approve. Creating an issue does not approve it.4
Run one build pass
Open a build session and invoke The builder repairs eligible rework first. Otherwise, it claims the oldest
safe ready issue, implements it in an isolated worktree, and opens a PR.
gsd-loop-build. In Codex:5
Run one review pass
Check review readiness:Open a separate review session and invoke Read the verdict. Blocking findings return the PR to
gsd-loop-review. In Codex:gsd:rework.
Complete evidence results in gsd:approved. Run another build and review
pass when repair is needed.6
Make the merge decision
Check the final diff, required CI, and review evidence. Merge the PR when
you are satisfied. The loop stops short of merging.
If setup reports that review is blocked because no successful CI check exists,
add real CI through a spec/build issue, wait for it to pass, then rerun
init.
Review does not treat missing required checks as success.