Quality

Automated Test Planning analyzes source code to identify coverage gaps, edge cases, and the tests a branch needs. Use it when you need a standalone test plan for files or directories, not manual test steps or test code.

Code Review guides an AI agent through a structured review process for changes. Use it to assess diffs for bugs, regressions, test gaps, YAGNI, and severity-ranked findings.

Code Walkthrough walks a person through code changes one step at a time, starting at the entry point and following the flow that changed. It is used to learn, teach, or prepare to review existing code before extending it.

Investigate traces software issues from symptoms back to root cause using evidence from code, logs, and tests. Use it when debugging bugs, failed integrations, or API behavior that needs a deep dive rather than a code review.

Manual Test Planning produces a plain-language manual test plan from provided context, including a summary, named tests, and step-by-step expected outcomes. Use it when you need acceptance walkthroughs, hand-tested QA steps, or a plan for a feature, change, branch, or pull request.

Refactor restructures existing code without changing behavior using a test-gated loop. Use it to clean up, simplify, or reshape code after tests are green and the target’s behavior is covered.

Test-Driven Development writes code through a test-first red-green-refactor loop with an observed-failure gate. Use it to implement features behavior by behavior from tests, including TPP or ZOMBIES ordering.

Debroid CLI Debugger orchestrates headless Android debugging via JDWP. Use it to set breakpoints, inspect runtime state, step through code, watch fields, and catch crashes in Kotlin or Java apps.

Debug UI drives the dev-3.0 app in headless Chromium to verify UI changes, reproduce visual bugs, take screenshots, and check console errors. Use it when you need to test the running interface instead of guessing from code.

Dev3 Bug Hunter runs read-only bug-hunting sessions with a seeded starting area and analysis style. It reports findings in a terminal-friendly format and can turn critical or medium issues into follow-up tasks that must reproduce the bug first.

Verify Changes explains how to test and verify work in dev-3.0, including which Vitest config covers each area, how to mock RPC and i18n providers, and what coverage is expected. Use it when writing tests, investigating failures, or preparing a change for review.

Verify Changes covers what to test for code changes, including vitest scope, mocking patterns, flake reproduction, and coverage expectations. Use it when validating a change against repo-specific verification gates and browser QA requirements.