sql-bench
Skill4 starsChanged 20 days agoMITView on GitHub
Read when changing queries.py, analyze SQL, symbols SQL, or sql.py.
In this repository4 other files it gives its agents.
- .cursor/rules/agent.mdcCursor rule
- new-commandSkill
- testSkill
- scip-cliSkill
The file
Files
SQL / query performance
Small fixture DB hides regressions on 40MB+ indexes. CI perf tests only catch gross mistakes on the tiny project.
Required before commit
Touching scip_cli/queries.py, scip_cli/analyze/*, scip_cli/symbols.py SQL, or scip_cli/sql.py:
scripts/bench.sh --baseline # once per change series
# … edit …
scripts/bench.sh --compareSynthetic scale: tests/bench_db.py + tests/test_bench_queries.py. Lines BENCH:<name>:<ms>; compare table ratio >1.0 = regression.
Correctness vs speed
- Behavior / SCIP shapes → fixture e2e (skill
test). - Graph plumbing only →
analyze_dbunit tests.
Optional: real cached index
Replace <project-slug> under ~/.cache/scip-cli/projects/ — snippet in agent.mdc § Large cached index benchmark.
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.

