test-issuelisted

<!-- requires: tester --> <!-- chains: none --> <!-- generated from .ai/workflows/test-issue.md; do not edit directly --> > **Codex:** this skill is the `/test-issue` adapter. Use Codex role agents from `.codex/agents/` when the runtime exposes them; otherwise perform the work directly and keep the same structured output. > Codex does not substitute `$ARGUMENTS` — read it as the arguments given in the user's request. Test the current implementation. Issue number (optional): $ARGUMENTS **Always delegate to role agent(s)** — test output is verbose and should not pollute the main context window. Steps: 1. **Detect repo**: Run `git remote get-url origin` to identify the target repo for `gh` commands. 2. **Identify changed files**: Run `git diff --name-only` and `git diff --cached --name-only` to see what's affected. 3. **Launch tester role agent(s)**: - Check CLAUDE.md to determine the correct test and lint commands for this project - Launch one or more tester role agents based on changed areas (parallelize if there are independent test suites) - Each tester runs in its own context and returns only a structured summary 4. **Verify acceptance criteria**: If an issue number was provided in $ARGUMENTS, run `gh issue view <#> --repo <detected-repo>` and check each acceptance criterion against the implementation. Report pass/fail per criterion. 5. **Report results** (concise — the role agents already absorbed the verbose output): - Tests: pass count, fail count,