Bring the context.
Provide pull request diff and description, repository conventions, test results and linked issues. Choose the systems and documents this team is allowed to read.
Engineering
Prepare a pull request review brief.
Summarize the change, examine test evidence and give reviewers a focused set of questions.
ContextReviewNext step
Change scopeAPI validation
Test evidenceCI results attached
ReviewTwo questions to resolve
Sources retainedOwner review
Illustrative output. Your records and rules shape the workflow.
CONNECTED TO YOUR STACK
Your systems. One coordinated workflow.
Bring context from the tools your team already uses. Connect MCP servers and APIs to read records, coordinate actions and keep the evidence together.
FROM INPUT TO OUTPUT
See how the work comes together.
Explore the request, the responsibilities and the handoff. Each step keeps the source context attached.
WHAT STARTS THE WORK
A pull request is opened or updated.
Corin uses the request together with the procedures and records you make available to this workflow.
01Pull request diff and descriptionContext
02Repository conventionsContext
03Test results and linked issuesContext
SPECIALIZED RESPONSIBILITIES
A team built around this task.
These example roles show how the work can be divided. Review the proposed team, models, tools and permissions for your process.
1
Code context agent
Read the diff alongside the issue and repository conventions to understand the intended behavior.
2
Validation agent
Review test results and identify missing evidence, edge cases and affected interfaces.
3
Review briefing agent
Prepare a concise review brief with file references and actionable questions.
READY FOR THE NEXT STEP
A review brief with change scope, validation evidence and unresolved concerns.
The result includes its source context so the responsible person can review it and decide what happens next.
YOUR WORKFLOW DELIVERS
- A review brief with change scope, validation evidence and unresolved concerns.
- Supporting records and source references
- Open questions and the accountable reviewer
WHERE THIS FITS
Prepare a pull request review brief with your own records and rules.
A pull request is opened or updated. The team needs pull request diff and description, repository conventions and test results and linked issues to make the next step useful.
Start with the procedure your team already follows. Corin uses that context to propose responsibilities and help coordinate the work across the tools you connect.
MAKE IT YOURS
Start with one process.
Review the responsibilities.
Use code context agent, validation agent, review briefing agent as a starting point. Set each role's tools, permissions and approval boundaries.
Check the first handoff.
Run a representative task. Compare the result with your procedure, review its sources and open questions, then refine the team before expanding the workflow.
KEEP EXPLORING
Other work your agents could take on.
WORKING DRAFTKeep documentation aligned with code changes
Code changeConfiguration updated
Affected docsSetup guide
PatchOwner review
Engineering
GitHub
Slack
Notion+ more
Keep documentation aligned with code changes
Find documentation affected by a change and prepare a reviewed update with code references.
GitHubSlackNotion+ moreResearch & draftsExplore workflow
Version changeRelease notes reviewed
CompatibilityMigration checked
ValidationResults for maintainer
EngineeringGitHubSlackNotion+ more
Prepare dependency updates with test evidence
Bring release notes, compatibility concerns and validation results into a dependency update proposal.
GitHubSlackNotion+ moreTask coordinationExplore workflow
ContextReviewNext step
New requestAccount matched
TerritoryNortheast
OwnerRouting recommendation
Sales
Salesforce
Google WorkspaceSlack+ more
Route new leads with the right context
Match an incoming inquiry to an account, territory and owner so the next conversation starts informed.
SalesforceGoogle WorkspaceSlack+ moreRouting & handoffsExplore workflow
OPEN SOURCE AT THE CORE
Build this around your way of working.
Give Corin your procedures, connected context and approval rules. Review the agent team, then put it to work.