testing
Skill70 starsChanged 7 days agoApache-2.0View on GitHub
Run the test tiers a code change in cap-evolve needs before review - the unit tier always, and a real end-to-end run (local zero-API or a dispatched CI benchmark/integration-test leg) when the change plausibly affects a real run. Use for every code change (core/cap_evolve, skills, dashboard backend, adapters, CI). Not for dashboard-frontend-only or docs-only changes - those have their own skills.
- Installs packages
194 other projects use a version of this.
Adopted by
Most recently taken up by
- magnusrodseth/dotfilestheir own version, first seen Nov 16, 2026
- NVIDIA/nvcftheir own version, first seen Nov 15, 2026
- adelrodriguez/skillstheir own version, first seen Nov 15, 2026
- pastropsucez/vibe-stacktheir own version, first seen Nov 15, 2026
- theishandubey/dotclaudetheir own version, first seen Nov 15, 2026
- igoroliveirg/claude-copytheir own version, first seen Nov 15, 2026
Used with
Projects with it also use bundle-dependency-prs, update-library-template and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillbundle-dependency-prs
Fix broken dependency update PRs and aggregate the ones that work into one PR.
Also in 7 projects that use this
MicrosoftSkillupdate-library-template
Merges the latest Library.Template into this repo (at position of HEAD) and resolves conflicts.
Also in 7 projects that use this
zetaloopSkillassign-copilot
Assigns a GitHub issue to the Copilot coding agent, optionally specifying a custom agent. Use this when asked to assign an issue to Copilot or delegate an issue to CCA.
Also in 3 projects that use this
NVIDIA-NeMoSkillbuild-and-dependency
Dev environment setup for Megatron Bridge — container-based development, uv package management, lockfile regeneration, adding dependencies, Slurm container usage, and common build pitfalls.
Also in 3 projects that use this
timmo001Skillchangeset-scope
Keep all scoped code work contained to the user-defined changeset. Use for implementation, fixes, diagnosis, refactoring, cleanup, and review when explicit instructions, named files, diffs, branches, pull requests, or injected work scopes define the boundary.
Also in 3 projects that use this
JetBrainsSkillmodule-dependencies
Add or modify IntelliJ module dependencies in `.iml` files.
Also in 3 projects that use this
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- modelcontextprotocol/servers★ 92ksame name
- lobehub/lobe-chat★ 86ksame name
- lobehub/lobehub★ 86ksame name
- penpot/penpot★ 62ksame name
- meteor/meteor★ 45ksame name
- iOfficeAI/AionUi★ 34ksame name
- garrytan/gbrain★ 33ksame name
- OpenZeppelin/openzeppelin-contracts★ 27ksame name
- tursodatabase/turso★ 25ksame name
- redis/go-redis★ 22ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- dashboard-changeSkill
- docs-changeSkill
- open-prSkill
- review-cyclesSkill
- agent-optimizeSkill
- evographSkill
- gepaSkill
- hill-climbSkill
- skilloptSkill
- mcp-toolSkill
- skill-packageSkill
- system-promptSkill
- toolsSkill
- wikiSkill
- run-optimizerSkill
- orchestrateSkill
- using-cap-evolveSkill
- baselineSkill
- diagnoseSkill
- evaluateSkill
- finalizeSkill
- gateSkill
- implement-and-checkSkill
- intakeSkill
- reportSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 174 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 38
Run this tier when the change touches: core/cap_evolve/harness.py or the optimization loop, an adapter (benchmarks/), the gate/seal/splits …
“Common” is measured: kept by at least 6 in 10 of the 174 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Testing
Two tiers. Run tier 1 always. Run tier 2 whenever the change could plausibly alter what a real optimization run does, scores, or costs — not just whenever you feel like it, but err toward running it when in doubt.
Tier 1 — unit (always)
The exact commands CI runs (.github/workflows/ci.yml, mirrored in
.bob/rules/01-cap-evolve.md):
pip install -e "./core[dev]" -e "./dashboard/backend[dev]"
python -m pytest core/tests -q
python -m pytest dashboard/backend/tests -q
python skills/_registry/build_manifest.py skills
python skills/_registry/lint_skills.py skills
cd dashboard/frontend && npm ci && npm run build && npm test- A change under
core/cap_evolve/,skills/*/*/scripts/,dashboard/backend/capevolve_dashboard/, ordashboard/frontend/src/needs a new or updated test in the matching*/testsdir. Flag its absence as a blocker, don't just note it. dashboard/frontend/dist/is committed — after anydashboard/frontend/src/change,npm run buildand commit the newdist/. CI fails on a staledist/.- Any new/changed skill needs its own
scripts/check.pygreen:python skills/<component>/<skill>/scripts/check.py. python -m compileall core skillsas a cheap final syntax pass.
Tier 2 — end-to-end (when the change can affect a real run)
Run this tier when the change touches: core/cap_evolve/harness.py or the
optimization loop, an adapter (benchmarks/**), the gate/seal/splits logic, the
CLI (cap-evolve run/init/check), or CI's benchmark dispatch
(ci/benchmarks/**, .github/workflows/benchmarks.yml,
.github/workflows/integration-tests.yml).
Zero-API, always free — run this first
bash benchmarks/toy/examples/calc/run.sh
cap-evolve init -y && cap-evolve check .capevolve/project
bash ci/e2e_all_algorithms.sh # all 5 algorithms, deterministic + agent-mode handoffThese cost nothing and catch most regressions in the loop itself. Always run them before a real dispatch, not instead of it, when the change is loop-adjacent.
Real model runs — only when zero-API isn't enough
Some changes (a new adapter, a scoring fix, a provider-routing change) need a real model to actually exercise. Dispatch from Actions, not by running the benchmark harness by hand on your own machine with live credentials:
Integration tests(.github/workflows/integration-tests.yml,workflow_dispatch): one cheap single task per leg (tau2,tau2_sierra,tau2_sierra_blackbox,appworld). Use this for "does the arm still land" after a wiring/adapter change — minutes, not dollars.Benchmarks(.github/workflows/benchmarks.yml,workflow_dispatch): the curated multi-task tiers (smoke/pilot/full) per benchmark. Use this when you need a real reward/latency/cost delta, not just "does it run".
gh workflow run "Integration tests" --repo skillberry-ai/cap-evolve -f bench=tau2_sierra
gh workflow run "Benchmarks" --repo skillberry-ai/cap-evolve -f bench=tau2 -f tier=smoke
gh run watch --repo skillberry-ai/cap-evolve # or: gh run list, then gh run view <id>Model provider order (apply this whenever you pick a model for either
workflow): RITS (ibm-rits/…, no budget) → ETE-INT (ibm-ete-int/…, the
team's main gateway) → ETE (ibm-ete/…, a second gateway with its own
budget) — use ETE only when ETE-INT can't serve the model or is over budget. Pick
a plain model name (e.g. claude-opus-5) and CI applies this order itself;
pick a prefixed id (ibm-ete/aws/claude-opus-5) only to pin one gateway
deliberately, and say why in the PR. The order and model list live in
ci/benchmarks/model_catalog.txt — read its header before adding a model. After a
run, the job summary and run record (agent_provider, optimizer_provider,
*_provider_skipped) show which provider actually served it; report spend per
provider from these. Full detail: ci/benchmarks/README.md, "Model providers and
their order".
Report the evidence
Once a real run finishes, post a PR comment (or put it in the PR description
before opening) with: the workflow run link, the leg/tier, the provider that
served it, and the key numbers (best_val, test_reward, test_delta, cost).
Reviewers in review-cycles read this instead of re-running anything themselves.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

