ENGINEERING
Auto-triage Sentry issues with unsymbolicated stack frames
When a new Sentry issue arrives, an agent inspects its stack trace for minified frames, diagnoses the likely source-map cause.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry new-issue webhookSentry
- ActionAgent gathers release artifacts and event detailSentry
- LogicClassify: real bug vs source-map failure
- ActionOpen GitLab fix-it issue with remediation (map-failure path)GitLab
- OutputTag issue and notify owning team (real-bug path)Slack
What it does
It watches incoming Sentry issues and singles out the ones nobody can debug — those with minified, unsymbolicated frames. An agent reads the trace, checks the release's artifacts, reasons about why symbolication failed (missing maps, mismatched release, wrong dist), and produces an actionable diagnosis instead of a raw alert.
When to use it
Use it when your error inbox is polluted by unreadable stack traces and engineers waste time figuring out whether it's a real bug or just a broken-maps artifact. The agent does that classification for you.
How it works
- 1A Sentry new-issue webhook fires with the issue and its stack frames.
- 2An agent step pulls the associated release artifacts and event detail from Sentry.
- 3It reasons over the evidence to decide: genuine bug, or source-map failure, with a confidence note.
- 4A logic branch routes the outcome by category.
- 5For map failures it opens a GitLab issue with the exact misconfiguration and fix steps; for real bugs it tags the issue and notifies the owning team in Slack.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.