PR Impact Badge
Zero-config architecture review on every pull request. PRISM posts an impact analysis comment the moment a PR is opened.
How it works
Create a GitHub App in your organization or account settings, then install it on the repositories you want to analyze.
→ Create GitHub AppPermissions needed: Pull requests: Read & write, Webhooks
In your GitHub App settings, set the Webhook URL to your PRISM instance:
https://your-prism-url/api/github/webhookOnce installed, PRISM automatically analyzes changed files on every PR and posts an impact badge comment. No configuration required on the developer side — it just works.
Live Demo
What developers see on their PRs🟡 PRISM Architecture Impact
Impact Score: 45/100 · Risk: Medium
Summary
This PR affects 2 architectural capabilities: Authentication, Payment Processing. ⚠️ 1 of these already has architectural drift.
Affected Capabilities
AuthenticationPayment Processing
Recommendations
- Review drift in: Authentication
- Request architecture review before merging
🔬 Powered by PRISM0x2A · Architecture intelligence for engineering teams
Setup
https://your-prism-url/api/github/webhookPaste this into your GitHub App webhook settings.
Never stored in plain text — saved only to verify webhook signatures.
Set GITHUB_TOKEN env var on your PRISM server instead for production deployments.
Test Analysis
Paste a list of changed files (one per line) to see what impact analysis PRISM would produce.