REPRODUCIBLE WORKFLOW SPECIFICATION
Production incident triage with Sentry, GitHub, Linear, and Slack
REVIEWED SEPTEMBER 2, 2026 / NOT A CUSTOMER PERFORMANCE CLAIM
Produce a verified incident packet, create or update the correct engineering issue, and prepare a Slack update without claiming the incident is resolved.
EXECUTION ORDER
Actions, purpose, and confirmation
- 01Sentry
list_organization_issuesFind unresolved issues in the named production project and time window.
No confirmation for a bounded read.
- 02Sentry
get_issue_eventRetrieve representative event evidence and sanitize sensitive fields.
Confirm before expanding into customer or request data.
- 03GitHub
list_commitsCompare the issue timing with recent repository changes.
No confirmation for repository metadata reads.
- 04Linear
create_linear_issueCreate a new issue only when no matching issue exists.
Confirm team, priority, owner, title, and evidence links.
- 05Slack
post_messagePublish the verified summary and Linear link.
Confirm channel and final message before posting.
Verification checklist
- Sentry issue and event URLs resolve.
- The suspected commit is described as correlation, not proven causation.
- The Linear issue contains sanitized evidence and has the intended team and owner.
- The Slack response returns a channel, timestamp, and permalink.
Known limitations
- This is a documented reference workflow, not a customer performance claim.
- Model classification cannot replace engineering diagnosis.
- Sentry payloads and Slack conversations may contain sensitive information.
- A successful ticket or message does not mean the production incident is fixed.
How to run this workflow safely
Begin with discovery and read-only actions, then verify the selected accounts before any write. Ask for confirmation at the step where the workflow becomes externally visible, financial, destructive, or difficult to reverse. Keep the structured result from every action so the final response can separate completed work from skipped, rejected, or failed steps. Retry only operations that are safe to repeat or protected by an idempotency key.