Brief reviewers on pull requests
Connect
SPIRITT
EntelligenceEntelligence
Codebase answers, put to work
SPIRITT adds your GitHub repositories to Entelligence, with docs, issues and pull requests ingested, then turns its codebase answers into onboarding guides, architecture docs, review briefs and tickets.
What you can do with Entelligence.
Any repo, indexed on demand
Add public or private GitHub repos by branch, with documentation, issues and pull requests pulled into the analysis.
Answers that become artifacts
SPIRITT questions the repository agent in multi-turn threads and ships the answers as docs, tickets and guides.
Built into the engineering loop
Codebase findings land in GitHub, Linear, Notion and Slack, where the team already works.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for codebase knowledge and engineering documentation.
02
Connect Entelligence
Connect Entelligence, plus GitHub and the apps where findings should land.
03
Hand over the mission
Name the repositories and the outcome. SPIRITT indexes them, asks the hard questions and delivers the result.
Hand over a mission.
Choose a mission. Make it yours.
Put Entelligence to work.
Put your codebase knowledge to work
Questions
Entelligence, with SPIRITT.
01What does SPIRITT do with Entelligence?+
It adds GitHub repositories for analysis, asks the repository agent about architecture, behavior and dependencies, and turns the answers into docs, tickets, briefs and bots.
02Can it analyze private repositories?+
Yes. Private repos are added with a GitHub access token, and you can choose the branch to analyze.
03Does it include issues and pull requests?+
Yes. Docs, issues and pull requests can be ingested alongside the code, plus a link to external documentation.
04Can it ask follow-up questions?+
Yes. SPIRITT passes conversation history with each question, so it can drill from architecture down to a single function.
05Where do the answers end up?+
Wherever the mission needs them: Notion or Confluence docs, Linear or Jira tickets, GitHub PR comments or Slack threads.
06What does the connection need?+
Entelligence connects without a separate key in SPIRITT. Private repositories need a GitHub access token supplied when they are added.