test-and-fix

Preamble

Read the user's requested test scope and commands, project instructions, test configuration, and relevant source files. Use the project's existing delivery or task records when they help establish the expected behavior.

Identify the target: web UI, API, command-line tool, library, or another artifact. Testing can run on the current branch, including the base branch. Inspect existing changes before editing.

Phase 1 — Analyze what changed

Use the supplied scope first. When testing changes, inspect the relevant staged, unstaged, or committed diff and trace its callers and consumers. Determine the comparison ref from the task or repository configuration; fetch only when the comparison needs updated remote information.

Map the affected behavior:

• Web UI: pages, components, interactions, and rendered states.
• API: endpoints, authentication, inputs, responses, and errors.
• CLI: arguments, input/output, exit codes, and file effects.
• Library: public functions, callers, return values, and edge cases.

For tests requiring a running service, find the startup command and address in project configuration, documentation, or existing process output. Start the required local service within the task's authorization. Ask only for essential information that cannot be established from available evidence.