AAWEA.ORG

Manual start

↓

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.

↓

✓

Exit condition: manual

Loop goal achieved

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Run loop") Exit{"Loop goal achieved"} S0 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Run "cardxc" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

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.

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

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