Menu
Run CI pipeline checks (trace + score + optional diff)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | ci |
| description | Run CI pipeline checks (trace + score + optional diff) |
| argument-hint | ["--baseline path"] |
| allowed-tools | Bash, Read |
Run Scalpel's CI pipeline to validate code health.
cargo build --release -p scalpel-cli
cargo run -p scalpel-cli -- ci \
--coverage-dir .scalpel/coverage \
--format text \
${ARGUMENTS}
Call graph soundness framework: 9 pattern families, 10 safety vetoes, soundness-vs-precision tradeoffs. Use before changing merge.rs, analyzer, or prune pipeline.
Assess if a CVE in a dep is reachable from project code using 15-signal union (runtime/static/external). Outputs audit trail. Security-grade, conservative.
Runtime+static consensus: 15-signal weights, modes, saturation curve. Scalpel's novel moat. Use before changing tracer merge, prune decision, or adding signal sources.
Use to validate Scalpel's pruning safety on any Python project. Analyzes a real-world Python project with test suite, identifies dead code, stubs it, then runs the full test suite to prove nothing broke. Invoke with: /prune-safety-test <project-url-or-path>
Use to validate ALL Scalpel capabilities on a real-world Python project — static analysis accuracy, genome building, reachability classification, pruning safety, and context generation. Invoke with: /validate-on-project <project-url-or-path>
Use when working on scalpel-core, scalpel-proto, Code Genome graph structure, hybrid merge logic, reachability algorithms, confidence classification, or edge resolution