ワンクリックで
test
Run tests, analyze failures, and fix until green
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Run tests, analyze failures, and fix until green
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guided git commit workflow — review changes, draft message, stage, commit
Manage context pressure during large codebase work without losing critical state.
Create a pull request with structured summary and test plan
Interactive debugging — reproduce, isolate, trace, fix
Explore a codebase or directory to understand its structure and purpose
Implement a requested code change end-to-end with scoped edits and verification.
| name | test |
| description | Run tests, analyze failures, and fix until green |
| when_to_use | After writing or modifying code that has tests, or when asked to test |
| required_tools | ["bash"] |
| tags | ["testing","verification"] |
| activation | {"input_patterns":["(?i)(run test|test.*fail|fix.*test|测试|跑.*测试)"]} |
${ARGS}
Identify the test framework and run command: Cargo.toml → cargo test, package.json → npm test / jest / vitest, pytest.ini / pyproject.toml → pytest, Makefile / justfile → look for test targets.
Execute the full suite (or scoped to the relevant module if the change is isolated). Capture stdout and stderr completely.
For each failure: read the failing test to understand what it expects, read the implementation it tests. Determine — is the test wrong or is the code wrong? If the code changed recently (git diff), the code is likely at fault.
Apply the minimal fix. One failure at a time. Re-run after each fix to verify no regressions.
State: how many tests, how many passed, what was fixed. If anything remains broken, explain why and what is needed.