Skip to content

docs: add /review-pr CI causality blog post#82

Open
jflowers wants to merge 1 commit into
mainfrom
opsx/blog-review-pr-causality
Open

docs: add /review-pr CI causality blog post#82
jflowers wants to merge 1 commit into
mainfrom
opsx/blog-review-pr-causality

Conversation

@jflowers
Copy link
Copy Markdown
Contributor

@jflowers jflowers commented May 3, 2026

Summary

  • Blog post at /blog/review-pr-causality/ — "Your CI Failed — But Was It Your Fault?" covering the CI triage tax problem, causality classification table (PR-caused vs pre-existing vs unknown), fix-it-forward pattern (fix branches with dirty-tree guard and collision check), in-line PR comments (15-comment cap, human confirmation), and the complete review lifecycle (/review-council pre-PR + /review-pr post-PR).
  • Content sourced from unbound-force/unbound-force/.opencode/command/review-pr.md (548 lines).

Closes #64

…noise

- Write blog post with BA-001 narrative arc: CI triage tax problem,
  causality classification table (PR-caused vs pre-existing), fix-it-
  forward pattern with dirty-tree guard, 15-comment cap for in-line
  PR comments, and review lifecycle timeline (/review-council +
  /review-pr)
- Create OpenSpec artifacts with spec review and code review passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

blog: Your CI failed — but was it your fault? How /review-pr separates signal from noise

1 participant