Use after the targeted cases pass - choosing the adjacent behaviour this change can break from the PR's files and the component's links, and the per-repository smoke set
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
After the targeted scenarios pass, run a quick regression sweep of adjacent behaviour. Choose what to sweep from:
list_links — who else calls this component; a change to a shared API or schema can break every caller.Keep it in project memory (search_memory "regression smoke") so it accumulates across rounds instead of being reinvented each time: app boots, login works, primary navigation works, the main create/read flow works, the landing page renders with no console errors (Lighthouse errors-in-console or a manual console check). When a regression escapes to UAT, extend the set with save_memory so the next round catches it.
One screenshot at 360 and 1440 of the one or two most-used unchanged screens that share the changed component or design tokens — a token/layout change can break a screen nobody touched in this task.
Record swept cases as category: regression.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when writing acceptance criteria for a task - express each as an observable Given/When/Then that QA can execute, including negative cases
The English summary is being prepared. Showing the original description.
Use when the diff adds or changes an endpoint, resolver, RPC, job or query that takes an object id, a role check, a request binding or a tenant filter - BOLA/IDOR, function-level authorization, mass assignment and tenant scoping
The English summary is being prepared. Showing the original description.
Use on every UI change - semantic HTML, labels for controls, keyboard-navigable dialogs/menus, visible focus, and never color as the only signal
The English summary is being prepared. Showing the original description.
Use when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
The English summary is being prepared. Showing the original description.
How to work a task returned with review, QA or UAT findings. Use when a task is in need_revision or PR review comments are in your context.
The English summary is being prepared. Showing the original description.
Use when the repository keeps its alerting in code, or a person asks for alerts outside TaskTrooper - PrometheusRule YAML, a Cloud Monitoring alert policy in Terraform, a Datadog monitor, each routed to TaskTrooper's alert ingest URL so it opens an incident here
The English summary is being prepared. Showing the original description.