CI design gate: run ss-score + deterministic checks on pull requests
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 955
- Forks
- 87
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 33
Description
From ROADMAP.md — Now.
Run ss-score and the deterministic checks (validate-engine, validate-palettes, skill-contract checks) on PRs and attach the score plus named deductions as a check run. A design regression should fail CI the same way a broken test does.
Acceptance:
- GitHub Action workflow that scores changed artifacts on PR
- Check run output lists per-category score and named deductions
- Fails below the project lock's threshold (default 80)
- Dogfooded on this repository's own artifacts first
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ROADMAP.md and the ss-score, validate-engine, validate-palettes, and skill-contract entry points to understand how artifacts are scored and how the project lock threshold is exposed. The work is done when pull requests produce a check run with per-category scores and named deductions, fail below the default 80 threshold, and run successfully against this repository’s own artifacts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100