Send CI failures and reviews to owners
Connect
SPIRITT
GitLabGitLab work,
carried through to merge
SPIRITT turns issues into code changes, investigates failed jobs, and carries merge requests through your review rules. Give it a delivery mission across repositories, pipelines, and team tools.
What you can do with GitLab.
Issues become working changes
Move from a scoped issue to a branch, implementation, tests, and merge request with a clear record of what changed and why.
CI failures get resolved
Use job traces to separate transient failures from code defects, apply targeted fixes, and verify the next pipeline result.
Releases stay coordinated
Bring milestones, merge requests, approvals, and pipeline results into one delivery operation with explicit blockers and owners.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for the engineering delivery, repository maintenance, or release operations you want handled.
02
Connect GitLab
Connect GitLab with access to the projects your mission needs. Existing project permissions and branch protections govern its actions.
03
Delegate an outcome
Hand over a concrete goal, such as fixing a failing pipeline or building a feature. SPIRITT executes the work and verifies the result.
Hand over a mission.
Choose a mission. Make it yours.
Put GitLab to work.
Carry your next change through
Questions
GitLab, with SPIRITT.
01Can SPIRITT write code and merge GitLab merge requests?+
Yes. It can read repository files, create branches, commit multiple file changes, open and update merge requests, and merge them within the connected account's permissions. It can inspect diffs, discussions, and approvals before acting, with your required checks and branch rules governing delivery.
02What GitLab access does a mission need?+
Connect the GitLab account with access to the intended projects. Repository changes, pipeline operations, and project administration require the relevant permissions. SPIRITT can inspect project membership, including inherited access, to distinguish a missing permission from a workflow problem.
03How does SPIRITT handle failed GitLab pipelines?+
It can list pipeline jobs, read job traces, inspect the related code, retry failed or canceled jobs through pipeline retries, and trigger a new pipeline for a branch or tag. A recovery workflow can distinguish transient failures from defects, implement repairs, and check the resulting pipeline instead of repeatedly retrying blindly.
04Can GitLab work drive actions in other systems?+
Yes. SPIRITT can connect issue and merge request work to Slack coordination, use Sentry incident context to drive repairs, and publish release decisions in Google Docs. GitLab project webhooks can feed event-driven workflows, while scheduled checks can reconcile delivery status across those systems.
05What can SPIRITT build around our GitLab projects?+
It can build a release control room, review queue, engineering intake app, or a new application whose source and CI configuration live in GitLab. The system can link issues, commits, merge requests, and pipeline results so each delivery status has traceable evidence.
06How is this different from adding another GitLab CI job?+
A CI job runs a configured task inside a pipeline. SPIRITT can investigate failures, change repository files, open repair merge requests, and coordinate the surrounding work. It can also inspect aggregate merge request approvals; rule-level approval details depend on GitLab Premium or Ultimate.