Repository navigation
Review specs and plans in ordinary threads, in any format - #29
Merged
Merged
Conversation
The agents' instructions now cover a spec, plan or design doc (a Markdown plan, an OpenSpec change, an ADR): the request names its paths and commit and any validator output, and the reviewer applies a spec checklist. An implementation request can cite the approved thread under ## Spec; the reviewer reads it with pair history and reports departures, or says it couldn't find them. No message field changes. The Claude reviewer's allowlist gains pair history. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Y3kg5hjT2zSZM9qUEEinM
…ow security note Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012Y3kg5hjT2zSZM9qUEEinM
This was referenced Nov 6, 2026
Merged
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.
Summary
Step 2 of the plan to take pair beyond code review: spec review that works with any format and changes only the agents' instructions.
openspec validate. An implementation request cites the reviewed spec in a## Specsection: thread ID, paths, approved commit, and what changed since.## Specsection, the reviewer reads the thread withpair history <id>and reports where the code departs from the spec; if it can't find the thread or the spec, it says so instead of assuming the code conforms.--allowedToolsgainspair history, which is read-only and already inREVIEWER_COMMANDS.Codex approved it in pair thread 2026-11-06T03-18-42-475Z-a3027a. It noted that the commit in a
## Specsection is only what the author says it is: a Claude reviewer has no git access to check it.Test plan
npm test: 115 pass, including an assertion on the Claude reviewer's allowlist🤖 Generated with Claude Code