Have an agent investigate every new issue before a person does

Post a diagnosis with evidence, assumptions and reproduction results on each new issue.

Prompt

Evaluate and apply this CI technique to my repository: Have an agent investigate every new issue before a person does.

Post a diagnosis with evidence, assumptions and reproduction results on each new issue.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/triage-investigation.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How Mastra used this technique

Read what Mastra changed and follow the original sources.

Have an agent investigate every new issue before a person does

Translated to GitHub Actions

What Mastra built: Mastra Factory produces an investigation for each new issue: a diagnosis, supporting evidence, assumptions and reproduction results.
Your GitHub Actions version: An agent that investigates every new issue and posts a diagnosis, evidence, assumptions and reproduction results before a person looks.

Mastra's earlier intake bot supplied labels and a welcome comment. Factory produces an investigation the next person can use: a diagnosis, supporting evidence, assumptions and reproduction results. Its A2A investigation documented six failing reproduction assertions and identified the server integration as the owner. Mastra credits observational memory, which compresses file contents, searches and test output into a line-by-line log of the important items.

its A2A investigation documented six failing reproduction assertions and identified the server integration as the owner Source

Use it when: Many new issues are too vague to reproduce or come from setup mistakes, and each takes a person's time to sort.
Before applying it: Review the investigation's assumptions before planning starts, since an incorrect assumption upstream carries into every later stage.
GitHub Actions adaptation: Compare the source system with your own workflow before applying this translation.

How Mastra used this technique

Have an agent investigate every new issue before a person does

Company Playbooks