Ito Test With Subagent

Always run tests through the ito-test-runner subagent to keep the main thread high-signal.

Policy

• ALWAYS use this skill for running tests.
• ALWAYS dispatch the ito-test-runner subagent before any direct test command.
• Do not bypass this flow unless the calling agent explicitly requires full raw logs for deep harness debugging.

Required Pattern

1. Dispatch the ito-test-runner subagent (never run tests directly first).
2. Give scope (full suite or specific target like file/package/crate).
3. Ask for curated output only: command source, command, PASS/FAIL, duration, relevant failures, short actionable excerpt.
4. Use the returned signal to decide next step.

Prompt Template

Run tests using the ito-test-runner workflow.

Scope: <full suite | specific target>
Context: <optional reason, e.g. pre-commit check or regression verification>

Return only:
- Test command source (AGENTS.md or inferred)
- Command executed
- PASS/FAIL
- Duration if available
- If failing: failing tests and a 5-15 line actionable excerpt

Failure Handling

• If failure is clear, fix code/tests and re-run via ito-test-runner.
• If failure is ambiguous, request one additional run scoped to the failing target.
• Escalate to direct/manual execution only when curated output is insufficient.

Red Flags

• Running raw make test in the main thread before delegation
• Posting full unfiltered test logs to the calling agent
• Ignoring AGENTS.md command guidance
• Switching away from Makefile-first inference without a clear reason