What Changed
unbound-force PR #323 adds optional GitHub review posting to /review-council Code Review Mode (Fixes unbound-force/unbound-force#314, Phase 3 of unbound-force/unbound-force#177).
The council's consolidated multi-persona findings can now be posted as a GitHub PR review. Key new capabilities:
- PR detection: via
gh pr view or explicit PR number argument (e.g., /review-council code 42)
- Multi-persona aggregation: findings from all Divisor personas posted in a single review with per-persona sections
- Verdict mapping: APPROVE →
APPROVE, REQUEST CHANGES → REQUEST_CHANGES, APPROVE WITH ADVISORIES →COMMENT
- Pre-posting checks: duplicate review detection, stale review dismissal warnings, CODEOWNER warnings
- Human confirmation: required before any review is posted
- Protocol 2 unlock: Issue Linking conditionally enabled when explicit PR number provided
- Graceful degradation: full local-only behavior preserved when
gh unavailable or no PR exists
Why It Matters
/review-council was previously a local-only, pre-PR command. Users had to be present at the terminal to see the council's findings. With GitHub posting, the council's verdict is visible to PR authors and collaborators directly on the PR, bridging the gap between the local terminal
experience and PR collaboration.
This also changes the command syntax — /review-council now accepts an optional PR number argument (/review-council [N] or /review-council code [N]).
Pages That May Need Updating
- /review-council command reference: Document Step 7 (GitHub Review Posting), the new PR number argument, and the verdict mapping table
- Review workflow comparison: Update any table comparing
/review-pr vs /review-council — the council now has optional PR posting capability alongside its local review mode
- Getting started / review guide: If the guide references review commands, note that
/review-council can now optionally post to GitHub PRs
Reference
What Changed
unbound-force PR #323 adds optional GitHub review posting to
/review-councilCode Review Mode (Fixes unbound-force/unbound-force#314, Phase 3 of unbound-force/unbound-force#177).The council's consolidated multi-persona findings can now be posted as a GitHub PR review. Key new capabilities:
gh pr viewor explicit PR number argument (e.g.,/review-council code 42)APPROVE, REQUEST CHANGES →REQUEST_CHANGES, APPROVE WITH ADVISORIES →COMMENTghunavailable or no PR existsWhy It Matters
/review-councilwas previously a local-only, pre-PR command. Users had to be present at the terminal to see the council's findings. With GitHub posting, the council's verdict is visible to PR authors and collaborators directly on the PR, bridging the gap between the local terminalexperience and PR collaboration.
This also changes the command syntax —
/review-councilnow accepts an optional PR number argument (/review-council [N]or/review-council code [N]).Pages That May Need Updating
/review-prvs/review-council— the council now has optional PR posting capability alongside its local review mode/review-councilcan now optionally post to GitHub PRsReference
openspec/changes/review-council-github-posting/