loops!cardxc
A CI testing loop that automatically runs card exchange (cardxc) test suites, validates outputs, and reports results.
Use loop copies the kickoff. Share copies the loop link. Open in Cursor / Claude Code only pre-fill that prompt — they do not install hook files. Download loop saves a README and kickoff into .cursor/loops/cardxc-mqi8i0wc/ — no hooks required. How it works
- Do not modify the check command or exit criteria to force success
- Do not skip, disable, or bypass checks to pass the exit condition
- If stuck after several iterations, stop and report blockers instead of gaming metrics
- Do not weaken, delete, or skip tests to make the suite pass
- Do not replace real assertions with trivial always-pass tests
- Prefer fixing production code over patching tests to go green
Two separate pieces
- Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace between passes.
- 1
Copy or open the kickoff prompt
Click Use loop to copy the kickoff into your clipboard. Open in Cursor and Open in Claude Code only open the agent with that prompt — they do not configure automation for you.
- 2
Paste into your coding agent
Start a chat in Cursor, Claude Code, Codex, or any agent. Paste the kickoff. The prompt includes the goal, iteration limit, shell check, and first step.
- 3
Agent self-paces until done
The agent runs the loop: act → run check command → read output → repeat until the exit condition is met or max iterations is reached. No install step is required for prompt-only loops.
Full guide with Cursor /loop notes: How to install loops
1. Run loop
You are a CI testing agent for the cardxc project. Your job is to: 1. Run the full test suite using the available test runner (e.g., `npm test`, `pytest`, or equivalent) 2. Analyze any failing tests and identify root causes 3. Fix failing tests or flag them with a clear explanation 4. Validate that all outputs match expected results 5. Generate a concise test report summarizing passed, failed, and skipped tests Start by checking the project structure and available test commands, then execute the tests and report back.
You are a CI testing agent for the cardxc project. Your job is to: 1. Run the full test suite using the available test runner (e.g., `npm test`, `pytest`, or equivalent) 2. Analyze any failing tests and identify root causes 3. Fix failing tests or flag them with a clear explanation 4. Validate that all outputs match expected results 5. Generate a concise test report summarizing passed, failed, and skipped tests Start by checking the project structure and available test commands, then execute the tests and report back.
Related loops
Install and run the "Pre-Commit Guard" loop. Goal: block git commits when tests are failing. Between iterations run: npm test Exit when: tests exit 0 before each commit. Step 1: Before any git commit, run tests. Fix failures before committing.
Start the "Flaky Test Triage" loop. Goal: classify failing tests as flaky vs real and fix only real regressions Max iterations: 5 Between iterations run: npm test -- --testPathPattern=<failing-suite> Exit when: every failure is classified and real regressions are fixed or explicitly deferred Step 1: Run the failing suite multiple times. Classify each failure, fix real ones, and document flaky behavior. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.
Install and run the "Post-Merge Regression Guard" loop. Goal: smoke tests pass immediately after every merge or rebase. Between iterations run: npm run test:smoke Exit when: smoke suite exits 0. Step 1: After a merge, run smoke tests. Fix regressions before continuing other work.