Context Goblin
Code review that knows what your PR breaks in other repos
FreeCodeDevOpsAI4,714 impressions#2 of its week3 comments
Comments
>log in to comment@_5d0 we crawl the connected repos with an LLM + use deterministic route matching for discovering of downstream services and dependencies. It's done periodically or ondemand from our Dashboard
- Zain Sheikh· 2mo ago
The cross-repo map of routes, queues and shared tables is the part single-repo review bots always miss. Does it discover downstream services on its own or do you register each one?
Context Goblin started as an internal tool. Coding agents produce far more code than anyone can review by hand, and every reviewer we tried read the diff without reading what depends on it. What's in it today: - Call graph per repo, so it reviews the change against its real callers - Cross-repo map: routes, queues, shared tables and packages between your services - Customizable review agents for your specific needs - Bring your own MCP servers for ticket and org-specific context - GitHub App Happy to answer anything about how the context pipeline works.
Context Goblin reviews pull requests using call-graph analysis and cross-repo context to show downstream impact.
- for
- Engineering teams that need safe PR reviews across multiple repositories.
- pricing
- freemium · free trial
Key features
- Call-graph analysis — Resolves symbols touched by the diff and walks callers in other files.
- Cross-repo context mapping — Maps routes, queues, shared tables and package dependencies between repos.
- Customizable subagents — Add or edit subagents with prompts tailored to your stack and style.
- Verified findings only — Findings are checked against the codebase to avoid style nits and noise.
- MCP server integration — Connect external MCP servers (Jira, Confluence, Linear, Notion, etc.) for richer context.
Use cases
- Identify downstream services that will break from a PR change
- Validate that a change respects shared tables or queues across repos
- Customize review focus by adding subagents for security, performance, or style
Context Goblin vs alternatives
 Context Goblin |  Fluent CI | .svg?width=64) Devzero |  Pieces Copilot |  BuildShip | |
|---|---|---|---|---|---|
| Best for | Cross-repo impact aware code reviews | TypeScript-based CI pipelines | Fast release workflows | AI coding assistance | Visual backend building |
| Pricing | Freemium | Free | Subscription | Free | Free |
| DevHunt upvotes | 15 | 158 | 85 | 63 | 118 |
| Launched | Aug 2026 | Jan 2024 | Apr 2024 | Mar 2024 | Jan 2023 |
- Context Goblin vs Fluent CI: Fluent CI writes CI pipelines in TypeScript, while Context Goblin focuses on PR review with cross-repo impact analysis.
- Context Goblin vs Devzero: Devzero accelerates releases, whereas Context Goblin provides impact-aware code review before release.
- Context Goblin vs Pieces Copilot: Pieces Copilot is an AI coding sidekick for workflow assistance; Context Goblin is a specialized PR reviewer with call-graph context.
- Context Goblin vs BuildShip: BuildShip builds backends visually; Context Goblin analyses existing code changes across repos.
Context Goblin FAQ
How does Context Goblin know what other repos are affected by my PR?+
It crawls your organization’s repositories, builds a versioned dependency map, and includes the parts of that map that touch the diff.
Do I need to pay to try the tool?+
No credit card is required; the first crawl and first PR reviews are free.
What happens when the free credits run out?+
Reviews pause until you request more credits; nothing is charged or deleted automatically.
Can I add my own review logic?+
Yes, you can add custom subagents and connect your own MCP servers to provide additional context.
Which platforms does Context Goblin integrate with?+
It integrates via a GitHub App and can read data from any MCP server such as Jira, Confluence, Linear, or Notion.
Summarized by DevHunt from contextgoblin.com · Sep 27, 2026. Details may change; check the official site.
.png?width=64)
