You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Phase 5's read-only 'gh api .../pulls/<n>/comments --jq' is refused by the attribution hook as an unsigned post #135
Phase 5's prescribed command for reading a pull request's inline review comments is a read-only gh api call whose --jq template emits a literal Body: label:
Where an attribution hook is active, that command is refused with This gh command posts prose under <maintainer>'s GitHub identity but the body carries no attribution sign-off. The hook appears to match on gh api together with the word Body, and cannot distinguish a GET that formats a body field for display from a POST that supplies one. No phrasing satisfies it, because a GET has no body to sign.
The cost is not a blocked cycle — gh pr view <number> --comments returns the same information and is not refused — but a prescribed command that fails on first use, with a message pointing at attribution rather than at the real cause. That is easy to misread as a genuine policy violation, and easy to misread as evidence that the pull request has no review comments.
Suggested action
Replace the Phase 5 snippet with the forms that work:
and state what is lost: the path:line anchoring, which has to be recovered by reading each comment's quoted context. If per-file inline detail is genuinely needed, note that the --jq template must avoid emitting a literal Body: label — \(.path):\(.line) — \(.body) — so the hook does not match it. Worth stating explicitly that a refusal here is never evidence that no review comments exist.
Provenance
Routed upstream from dmccoystephenson/medieval-factions-dev-loop#46, where it was filed as template-rule. That instance has since been fixed locally — its Phase 5 no longer reaches for gh api at all — but the snippet is inherited from create-dev-loop.md, so every other generated skill still carries it.
Further observation from a gardener tend dispatch on 2026-11-05: the Phase 5 snippet was refused with This command requires approval, not with the attribution message quoted above, so the cause may differ between dispatches.
gh pr view <number> --json reviews was used instead. Copilot's review summary lists each finding's title and severity, which was enough to assess and fix all three findings on PR #175. The line anchors and the full inline text were not available. If the review summary had been absent, those findings would have been invisible, so an empty --comments result should not be read as no inline review.
Activity
dmccoystephenson commentedon Nov 6, 2026
Further observation from a
gardener tenddispatch on 2026-11-05: the Phase 5 snippet was refused withThis command requires approval, not with the attribution message quoted above, so the cause may differ between dispatches.gh pr view <number> --json reviewswas used instead. Copilot's review summary lists each finding's title and severity, which was enough to assess and fix all three findings on PR #175. The line anchors and the full inline text were not available. If the review summary had been absent, those findings would have been invisible, so an empty--commentsresult should not be read as no inline review.This comment was drafted during a Gardener session (https://github.com/Stephenson-Software/gardener).
drafted by Claude on behalf of Daniel Stephenson