원클릭으로
test-runner
Run the relevant tests for the current change and summarize results. Use in Flow 3 (Build) and optionally in Flow 4 (Gate).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Run the relevant tests for the current change and summarize results. Use in Flow 3 (Build) and optionally in Flow 4 (Gate).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.
Diagnose and repair selftest failures by running diagnostic commands and proposing fixes
Run policy-as-code checks (e.g., OPA/Conftest) based on the policy_plan. Use in Flow 2 and Flow 4.
| name | test-runner |
| description | Run the relevant tests for the current change and summarize results. Use in Flow 3 (Build) and optionally in Flow 4 (Gate). |
| allowed-tools | Bash, Read, Write |
You are a helper for running tests efficiently in this repository (Rust-focused).
Prefer scoped test runs:
git diff --name-only origin/main...HEAD to list changed files when available.Concrete commands for this repo (Rust):
cargo test -p <crate> -- <test-name-pattern> or cargo test --test <name> when a crate/test target is known.cargo test --workspace --tests --color=alwaysRuntime flags and speed:
Capture output and artifacts:
test_output.log (overwrite per run) and a parsed summary to test_summary.md.test_summary.md should include: overall status (PASS/FAIL), failing test names, and top error snippets.Failure handling:
test_summary.md.Do not modify source or tests.
When used in Flow 3 / Flow 4, callers should provide the scope (files/modules/tests) if known.