Run and import a Judge snapshot properly
Judge needs two visible lanes: a public scorecard lane and an operator import lane. This page is the operator lane. Run a pinned static scan to publish the public grade, then optionally attach an AI review as a second pass.
Public grade
Static, deterministic, and tied to one pinned commit. This is the score users see on the public Judge page.
AI review
Optional second pass for richer context. It is stored separately so Judge never feels like an arbitrary LLM grade.
Import route
This page posts to the existing admin import endpoint so you can stop guessing how to upload a snapshot.
Run the deterministic public-grade pass
Always pin the commit first. The public Judge grade should come from a reproducible static run, not from an AI pass.
git clone https://github.com/OWNER/REPO
cd REPO
git checkout <commit-sha>
skylos . --danger --secrets --quality --json -o judge-static.jsonOptionally add an AI review
If you want a second pass, import it as `agent`. That gives you an AI review trail without rewriting the public score.
# Optional second pass
# Use Skylos defend or another AI review tool that can export JSON
git checkout <same-commit-sha>
skylos defend . --json -o judge-agent.jsonAccepted report inputs
Skylos JSON: output from skylos . --json.
SARIF: any SARIF payload Judge can normalize into security, quality, secret, and dead-code findings.
Skylos defend JSON: valid for the optional AI review path.
Claude Code Security JSON or another normalized summary/findings payload.
What this fixes for users
The public Judge pages now explain what affects the score and what does not. The public grade is static. The AI review is separate.
This page gives operators a concrete place to import snapshots instead of hiding everything behind docs and an admin-only API contract.
When you are importing for an existing repo page, open this route with query params like /judge/submit?owner=psf&repo=black to prefill the form.