Implement and verify PR fixes
Connect
SPIRITT
GreptileGreptile
Code review becomes delivery work
Connect Greptile review findings, repository knowledge, and scoped review rules to your engineering workflow. Use actual review comments, stored addressed states, and citations to build an actionable engineering queue.
What you can do with Greptile.
Findings with source evidence
Use actual review comments, stored addressed states, and citations to build an actionable engineering queue.
Review rules that persist
Save explicitly scoped review guidance so future reviews use your team's conventions.
Repository knowledge in reach
Read published repository documents and connect them to implementation work while preserving truncation and source limits.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace to build a review operations app. Bring the operating rules and source records you want it to use.
02
Connect Greptile
Connect your Greptile account with access to the records and actions your mission needs. Connect the companion apps you want involved in the handoff.
03
Delegate an outcome
Start with: Build a review operations app. Define the account scope, approval rules, and destination for the result. SPIRITT runs the work and verifies the outcome.
Hand over a mission.
Choose a mission. Make it yours.
Put Greptile to work.
Code review becomes delivery work
Questions
Greptile, with SPIRITT.
01Can it turn review findings into work?+
Use actual review comments, stored addressed states, and citations to build an actionable engineering queue. Build a Supabase-backed queue showing severity, stored addressed state, and source references, then create Linear tasks for approved priorities.
02Can it save review rules for future runs?+
Save explicitly scoped review guidance so future reviews use your team's conventions. Retrieve the saved rule and record its ID in Notion for future review governance.
03How does it use repository knowledge?+
Read published repository documents and connect them to implementation work while preserving truncation and source limits. Build a Notion onboarding guide with source versions and GitHub source checks where documents are incomplete.
04What do I connect to get started with Greptile?+
Connect your Greptile account, identify the records or project scope for the mission, and provide the operating rules. For build a review operations app, start with the source inputs described in that mission and authorize the companion apps used for its handoffs.
05Does a new commit mean a finding was fixed?+
No. Greptile stores addressed flags, while commit timing only shows that commits occurred after a review. SPIRITT uses those distinct signals, inspects source changes through a connected repository, and verifies fixes before calling them resolved.
06Can it prove a repository has no matching review issue?+
Not from a truncated search. Review and knowledge searches have result or scan limits, and some document reads return only a prefix. SPIRITT narrows the query or inspects repository source when missing evidence matters.