Problem
Room can evaluate diffs via the room_check_diff MCP tool, but there is no automated pipeline that runs analysis on pull requests and posts results back. Teams need CI-native enforcement — a GitHub Actions integration (and eventually GitLab CI) that runs Room analysis on every PR and reports findings as review comments or check failures.
Proposal
Ship a GitHub Action (and reusable CI step) that:
- Runs on pull request events
- Sends the PR diff to Room for evaluation against the active ruleset
- Posts findings as PR review comments with file/line references
- Fails the CI check when the evaluation returns a blocked verdict
- Supports configuration via repository-level policy file or Room workspace binding
Later phases:
- GitLab CI template
- Status checks and required-check integration
- Inline remediation guidance in review comments
Why
MCP-sidecar and IDE hooks catch issues at generation time, but PR review is the enforcement backstop for code that was written without Room active. Most teams need both layers.
Problem
Room can evaluate diffs via the
room_check_diffMCP tool, but there is no automated pipeline that runs analysis on pull requests and posts results back. Teams need CI-native enforcement — a GitHub Actions integration (and eventually GitLab CI) that runs Room analysis on every PR and reports findings as review comments or check failures.Proposal
Ship a GitHub Action (and reusable CI step) that:
Later phases:
Why
MCP-sidecar and IDE hooks catch issues at generation time, but PR review is the enforcement backstop for code that was written without Room active. Most teams need both layers.