Agent kit for working on canonical/chisel-releases. Cross-agent skills + scripts for authoring and reviewing chisel slice definition files.
81
85%
Does it follow best practices?
Impact
75%
Average score across 5 eval scenarios
Low
Low-risk findings worth noting
The chisel-releases repository holds the chisel releases that chisel consumes: one Git branch per Ubuntu release, ubuntu-XX.XX (e.g. ubuntu-22.04, ubuntu-24.04, ubuntu-26.04).
main is meta-only: CI, workflows, contributing docs. No slices/ or chisel.yaml on main.maintenance.end-of-life in chisel.yaml.chisel.yaml's archives.ubuntu.version: ubuntu-24.04 <-> version: 24.04.Per-release branch root layout:
chisel.yaml # release manifest
slices/<pkg>.yaml # one SDF per package
spread.yaml # spread test config
tests/spread/integration/<pkg>/task.yaml # integration tests
tests/spread/lib/ # shared spread helpers
.github/ # workflows + CI scriptsActive branches accumulate hundreds of SDFs and keep growing; count a checkout with ls slices/ | wc -l (orientation prints this).
Live release list: run scripts/_orientation.py -- it discovers the branches, their format:, and which are still maintained (end-of-life vs today) -- or the repo README.md.