← Back to use cases
Pull context into a code review
The background — a spec from your docs tool, a note from your sales tool — shows up automatically, so you’re not hunting across tabs
Team
AI
Contributed by
JJ
JJ
The problem
A pull request rarely explains itself. The why lives in a spec, a ticket thread or a customer note — and finding it means leaving the review, which is where reviews go to stall.
What changes
The background arrives with the review. Specs, tickets and notes connected to the work surface next to the code, so you can judge the change with the full story in view.
How Humble helps
1
Connect your team’s tools
Image — Connections screen with docs and ticket tools linked
Link the tools where context lives — docs, tickets, CRM. Humble joins them up behind the scenes.
2
Open a pull request
Image — code review with the related spec shown alongside
Humble recognises the work it relates to and surfaces the linked spec, ticket or note beside it.
3
Review with the whole story
Image — reviewer reading code with the context panel open
No tab-hunting, no “what was this for again?” — the decision-making context is already on screen.
Set it up
- Connect GitHub from Settings, then Connections.
- Connect the tools where your specs and notes live.
- Open a pull request in your browser.
- Open the Humble extension — related context appears alongside.
Related use cases