Use when: analysing a project's test health — coverage, robustness, and CI integration.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Evaluates whether the project has a functioning, proportionate test suite. Assigns a score from 0.0 to 1.0 across two dimensions.
Coverage ratio — Are enough source files tested?
Test script — Can the suite be run?
tst_score = (coverage_ratio + test_script) / 2
Edge case: if no test files exist at all, score is 0.0 and only one critical task is generated.
When test suite execution fails: If the test suite cannot be executed (missing dependencies, syntax errors, unavailable runtime), record this as a data gap rather than failure; note it in output and do not penalize the coverage score until the execution blocker is resolved.
Score interpretation:
| Finding | Priority |
|---|---|
| No test files at all | critical |
| Test file ratio < 50% | high |
| No scripts.test in package.json | high |
When performing a manual TST analysis:
Output: ratio score, list of untested modules ordered by risk, and specific edge cases missing from existing tests.
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.
Universal guardrails loaded by every agent. Defines Verify Before Reporting (VBR), Write-Ahead Log (WAL), and the security baseline. Always-on, role-independent.
The English summary is being prepared. Showing the original description.
Use when: architecture mode, architect this, ADR, C4, PlantUML, system boundary, design decision, PRD gap, high ambiguity, multiple technical approaches, security architecture, data architecture, integration risk, implementability gap, story ticket, or epic ticket.
The English summary is being prepared. Showing the original description.
Use when: assumptions audit, audit assumptions, check for hidden assumptions, plan/ticket has ambiguous scope edges, pre-flight before finalizing a ticket, unstated assumptions, or 'what am I assuming'. Surfaces unstated assumptions, ambiguous scope edges, and untested preconditions in a finished plan/ticket/ADR before it is handed to Builder. Optional pass — Architect judges when to apply it; not a mandatory gate on every ticket.
The English summary is being prepared. Showing the original description.
Use when: Tester needs UI state evidence for VBR, or Builder needs to verify an integration wire is observable end-to-end. Powered by agent-browser MCP — token-efficient browser automation (200–400 tokens/page).
The English summary is being prepared. Showing the original description.
Use when drafting a bug or defect ticket, reviewing one someone else wrote, or deciding whether a reported problem is ready to file. Keeps what the reporter actually saw separate from what the agent later found out, so a reader can tell which lines are testimony and which are collected proof. Trigger phrases: 'file a bug', 'write up this defect', 'triage this report', 'is this ticket ready to file', 'what did the reporter actually see'.
The English summary is being prepared. Showing the original description.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
The English summary is being prepared. Showing the original description.