Reproduce a bug report on staging
Each step of the report tried on staging, with the result, the errors and screenshots, as a draft comment.
- You start it: When you start it
- Asks you first
What it does
The task
Read the Jira issue issue key: the steps, the expected result, the browser and the account type. Follow the steps on staging at staging url with the test account from the vault. At each step, record what happens, the console errors and the failed network requests, and take a screenshot when the result is not as expected. When the bug does not show, try one variant of the steps. Draft a comment for the issue with the result, the exact steps and the evidence. Ask me before you post the comment.
- It works in Jira and any website, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- It runs once, when you start it.
- It stops for your approval before it sends, posts, pays, books or changes a record.
What you give it
| Blank | What to give | Example |
|---|---|---|
| issue key | The Jira issue key | PAY-512 |
| staging url | The address of staging | https://staging.brightleaf.app |
What you get back
An example run with the example values above. Your run uses your own data.
PAY-512 "Discount disappears at checkout": reproduced
1. Add the Pro plan to the cart: OK, 120.00 USD
2. Apply the code WINTER20: OK, 96.00 USD
3. Change billing to yearly: the total is 1,440.00 USD. The discount is gone.
Network: POST /api/cart/interval returns the cart without the coupon field. Console: no errors
Variant: apply the code after the change to yearly: the discount stays.
Draft comment ready with 2 screenshots. Waiting for your approval to post.
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 issue key and staging url. Tab moves to the next blank.
- 03
Run it
Run sends it to the agent. Follow each step in the panel, and stop it at any time.
From the terminal
cuiar exec "Read the Jira issue PAY-512: the steps, the expected result, the browser and the account type. Follow the steps on staging at https://staging.brightleaf.app with the test account from the vault. At each step, record what happens, the console errors and the failed network requests, and take a screenshot when the result is not as expected. When the bug does not show, try one variant of the steps. Draft a comment for the issue with the result, the exact steps and the evidence. Ask me before you post the comment."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 run_task 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 run_task to run my "Reproduce a bug report on staging" template with issue key = PAY-512; staging url = https://staging.brightleaf.app.Setup for other agents: AI agents.
The tool call
{
"name": "run_task",
"arguments": {
"task": "Read the Jira issue PAY-512: the steps, the expected result, the browser and the account type. Follow the steps on staging at https://staging.brightleaf.app with the test account from the vault. At each step, record what happens, the console errors and the failed network requests, and take a screenshot when the result is not as expected. When the bug does not show, try one variant of the steps. Draft a comment for the issue with the result, the exact steps and the evidence. Ask me before you post the comment."
}
}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
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
Engineering
Find broken links on your website
Every link and image that returns an error, with the page it is on and the link text, in a sheet.
You start it: When you start it- Any website
- Google Sheets
Engineering
Check web pages for accessibility problems
WCAG 2.2 AA problems on each page, with the element, the rule and a fix, the blockers first.
You start it: When you start it- Any website
- Google Docs
EngineeringAsks first
Write release notes from merged pull requests
Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.
You start it: When you start it- GitHub
Engineering
Read the changelogs before you upgrade dependencies
Breaking changes, security fixes and upgrade steps for each outdated package, from its release notes.
You start it: When you start it- GitHub
- npm
- PyPI