Striffs for GitHub

An architecture diagram of every GitHub pull request, checked against the rules in the repository's own docs.

Striff helps you review pull requests at the architectural level, not just the file-diff level. Instead of forcing reviewers to reconstruct system impact from changed files and scattered comments, Striff generates a structural view of a pull request directly inside GitHub. You can see how classes, relationships and dependencies shift, where architectural risk is concentrated, and which parts of the system deserve the most attention before merge. Striff is built for teams reviewing modern pull requests, especially larger changes and AI-assisted code, where line-by-line diffs can look clean while deeper structural issues still slip through. What Striff helps you do: - See the architecture impact of a pull request before reading every file - Check a change against the architecture rules your team already wrote down in READMEs, ADRs and design docs - Catch coupling drift, risky structural changes and boundary shifts earlier - Attach a diagram of the affected components to your review comments - Review large or AI-generated PRs with more confidence - Understand change faster with visual structure, structural checks and review guidance in one place How it works: - Open a GitHub pull request - Click the Striffs button in the pull request toolbar - View a structural diff of the code changes. The first analysis of a pull request takes a few minutes; after that it loads instantly. - Inspect changed components, relationships and review findings without leaving the PR Supported languages: Java, C#, TypeScript and Python. Striff is useful for: - Engineers reviewing complex pull requests - Tech leads and architects watching for system drift - Teams adopting AI coding tools who need better review visibility - Organizations that want architecture-aware review workflows Privacy and data: To analyse a pull request, Striff sends its changed files, and the source and documentation from the base branch they depend on, to Striff's servers. The uploaded code is deleted once the analysis finishes; the resulting diagrams and review are kept so repeat views load instantly. Public repositories need no sign-in or token. Private repositories need a GitHub token, and we recommend a read-only fine-grained one, which the extension helps you create. The token is stored locally in your browser and sent with your requests so Striff can read the repository on your behalf; our servers use it per request and do not store it. Diagrams are also cached in your browser for up to a day. Clearing the token in the extension removes it along with the cached diagrams. For full details, see our privacy policy: https://striff.io/privacy/ Learn more: https://striff.io