Land reviewed Devin pull requests
Connect
SPIRITT
DevinDevin
Put a coding fleet on the roadmap
SPIRITT turns Devin into a coordinated engineering fleet. It splits roadmap work into Devin sessions, reviews and scans the pull requests they open, and keeps the playbooks, knowledge and automations behind them sharp.
What you can do with Devin.
Sessions with a dispatcher
Launch Devin sessions against the right repositories, follow their events, and gather results once every session settles.
Reviews and scans on demand
Trigger Devin Reviews on pull requests, act on findings by severity, and run code scans with targeted remediation.
A codebase that answers back
Ask grounded questions about indexed repositories, generate missing wikis, and keep playbooks and knowledge notes current.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for engineering delivery. Bring the backlog, repositories and standards Devin should work from.
02
Connect Devin
Connect your Devin organization, then add GitHub, Linear or Slack so sessions, pull requests and status updates land where your team works.
03
Delegate an outcome
Describe the outcome, the repositories in scope and how work gets accepted. SPIRITT splits it into Devin sessions, reviews the output and reports what shipped.
Hand over a mission.
Choose a mission. Make it yours.
Put Devin to work.
Put a coding fleet on the roadmap
Questions
Devin, with SPIRITT.
01Can SPIRITT start Devin sessions for us?+
Yes. It creates sessions against chosen repositories with tags and structured outputs, sends follow-up messages, and waits for a whole batch to settle before reporting.
02Can it review pull requests with Devin?+
Yes. It triggers a Devin Review on a pull or merge request in a connected repository, reads the status and findings by severity, and acts on them.
03Can it set up event-driven Devin automations?+
Yes. Devin automations fire on GitHub activity, Slack messages, Linear updates, schedules or incoming webhooks. SPIRITT creates, tunes and audits them.
04Does it understand our codebase?+
It asks questions against Devin's repository wikis, reads their structure and contents, and generates a wiki for any repository that lacks one.
05Can it run and remediate code scans?+
Yes. It runs scans with include and exclude paths, reviews findings, and starts remediation on the ones you prioritize.
06How do we track Devin usage?+
Billing tags group sessions by team or project. SPIRITT creates tags, assigns sessions, and reports usage by tag.