Triage new errors in Sentry
New and returning errors since the last run, with users affected, the suspect commit and draft issues.
- On a schedule: Every weekday at 9:00
- Asks you first
What it does
The task
Open the Sentry project project and list the issues that are new or that came back since the last run. For each one, read the error message, the stack trace, the number of events and users, the release and the suspect commit. Mark the issues that affect more than min users users or that happen in the checkout or sign-in flows. Draft a Linear issue for each marked one with the stack trace, the steps from the breadcrumbs and the Sentry link. Ask me before you create the Linear issues. Do not resolve or ignore anything in Sentry.
- It works in Sentry and Linear, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- As a routine it runs every weekday at 9:00 (cron
0 9 * * 1-5). - It stops for your approval before it sends, posts, pays, books or changes a record.
What you give it
| Blank | What to give | Example |
|---|---|---|
| project | The Sentry project | brightleaf-web |
| min users | The number of users that makes an error important | 50 |
What you get back
An example run with the example values above. Your run uses your own data.
Sentry brightleaf-web: 6 new or returning issues since Tue 9:00
| Error | Events | Users | Release | Suspect commit |
|---|---|---|---|---|
| TypeError: rows is undefined (export.js:88) | 412 | 96 | 2.5.0 | 4f2c91a Fix invoice totals |
| ChunkLoadError: Loading chunk 812 failed | 77 | 54 | 2.5.0 | none |
| StripeError: No such price (checkout.ts:41) | 19 | 17 | 2.4.2 | 9b10e7d Add yearly plan |
... 3 more below the limits
Marked: export, chunk load, checkout
3 Linear drafts ready. Waiting for your approval to create them.
Run it in Cuiar
- 01
Open it
Click Use in Cuiar on this page. The side panel opens with the task in the composer.
- 02
Fill in 2 blanks
Type project and min users. Tab moves to the next blank.
- 03
Run it, then repeat it
Run sends it once. To run it every weekday at 9:00, make a routine on cuiar.com/routines or with the CLI below.
As a routine, from the terminal
cuiar routines create "Triage new errors in Sentry" --schedule "0 9 * * 1-5" --time-zone Europe/Berlin \
"Open the Sentry project brightleaf-web and list the issues that are new or that came back since the last run. For each one, read the error message, the stack trace, the number of events and users, the release and the suspect commit. Mark the issues that affect more than 50 users or that happen in the checkout or sign-in flows. Draft a Linear issue for each marked one with the stack trace, the steps from the breadcrumbs and the Sentry link. Ask me before you create the Linear issues. Do not resolve or ignore anything in Sentry."Run it from your AI agent
Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call create_routine yourself.
1. Add Cuiar to Claude Code
claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp2. Ask your agent
Use the Cuiar tool create_routine to run my "Triage new errors in Sentry" template with project = brightleaf-web; min users = 50.Setup for other agents: AI agents.
The tool call
{
"name": "create_routine",
"arguments": {
"name": "Triage new errors in Sentry",
"task": "Open the Sentry project brightleaf-web and list the issues that are new or that came back since the last run. For each one, read the error message, the stack trace, the number of events and users, the release and the suspect commit. Mark the issues that affect more than 50 users or that happen in the checkout or sign-in flows. Draft a Linear issue for each marked one with the stack trace, the steps from the breadcrumbs and the Sentry link. Ask me before you create the Linear issues. Do not resolve or ignore anything in Sentry.",
"schedule": "0 9 * * 1-5",
"time_zone": "Europe/Berlin"
}
}Related templates
All engineering templatesOps
Write a weekly project status report
Done, in progress, late and blocked work from your project tool, added to one status doc.
On a schedule: Every Friday at 14:00- Asana
- Jira
- Linear
- +1 more: Google Docs
Ops
Draft the agenda for your weekly team meeting
Open actions from last week's notes, new topics from the team channel and blocked work, with times.
On a schedule: Every Monday at 15:00- Notion
- SSlack
- Linear
Engineering
Sort the security alerts in your repositories
Open Dependabot alerts across your repos, grouped by package, with the fix version and any open fix PR.
On a schedule: Every Monday at 9:30- GitHub
Engineering
List pull requests that wait for review
Open PRs across your repos with age, reviewers and CI status, the oldest first.
On a schedule: Every weekday at 10:00- GitHub
Engineering
Run a smoke test on staging after each deploy
Sign-in, key pages and main actions checked in the browser, with a screenshot of each failure.
On an event: When a new staging deploy finishes- Vercel
- Any website
Engineering
Test your checkout with Stripe test cards
Each payment case run in test mode, from a good card to a declined one, with what the buyer sees.
You start it: When you start it- Stripe
- Any website