ShipSignal — AI impact
crown · 2026-02-05 → 2026-06-17 · 19.0 weeks · 726 commits
AI Adoption
Pervasive97%
Claude 705 · lower bound
Delivery Health
55/100 F
general eng norms
Readiness
83/100 B
static repo state
AI adoption 97.1%
(705/726 commits — lower bound)
Adoption date: 2026-02-02
Rate / week: ███▇█▇▇███████▇████
Delivery Health (general norms, NOT AI-attributed)
change_size_discipline
100%
test_discipline
10% low test discipline
knowledge_distribution
n/a (solo author)
Context (not scored): fix/revert 26% · 38.21 commits/wk · 1 contributors.
Before/after AI Enablement (bonus)
n/a — AI adoption is at or before repo inception — no pre-AI window to compare
A before/after needs a clean pre-AI baseline; the three numbers above stand on their own.
Attribution caveat. Delivery pillars (flow, quality, risk) measure GENERAL delivery health — only AI-adoption and readiness are AI-specific. A delivery change may come from hiring, a finished migration, or a calmer quarter. The score asks whether the conditions under which AI pays off are improving — it does NOT prove AI caused any change.
shipsignal v0.1.0 · 2026-06-19T20:49:45Z
Readiness — 83/100 · B
Top Readiness fixes (4 total)
- scripts — Module 'scripts' (dir) has no README
→ Add scripts/README.md describing this module - src/scenes — Module 'src/scenes' (dir) has no README
→ Add src/scenes/README.md describing this module - . — Missing CI configuration
→ Add CI (e.g. .github/workflows) so agents can see how it's built and tested - . — Missing type config
→ Add type config (tsconfig.json / mypy / pyright / py.typed)