Phase 04 · Operate
Incident → commit
How it works
Root-cause analysis starts with code context instead of a cold search – even without the one senior who knows it all.
- Correlates the incident with the most recently changed components
- Suggests the commits and PRs that likely caused it
- Names the owner who last changed the affected code
- Captures the learning for the next cycle
Roles
Head of product & engineering
Teklens apps & integrations
Teklens.aiGitHubJira
Example prompts & actions
Copy one of the following prompts and paste it into the Teklens chat. Adapt the details to your use case.
Which commits could have caused incident [ID]?
Who last changed the affected code?
Summarise the likely cause and the owner for incident [ID].
Related use cases
Three use cases closely connected to this one.
Bug triage and resolution without senior capacity.Triages bugs, finds the likely cause in the code and prepares the resolution – or executes it.View use case Auto-triage & dispatchTriages and dispatches every new support issue automatically – first-response time drops.View use case Runbooks & postmortemsGenerates runbooks with root-cause analysis – and turns closed incidents into postmortem drafts.View use case
From the PM Lab
Articles that explore this use case in depth.
Give Teklens a real job.
Connect Jira and your code – and let Teklens work on something real.