Skip to content

Quality baseline ​

The checks that every project in this family runs, and where to copy them from. The files are in baseline/; linked-codebook itself is the strictest example.

ConcernBaselineWhere
One entry pointmake check = lint, types, tests, size; CI runs exactly thatbaseline/Makefile
Python lint and dead coderuff, pinned to one minor version; unused names, unused arguments, commented-out codebaseline/ruff.toml
Python typesmypy --strict on the cleaned modules; ty as an advisory job until it leaves betaMakefile
TypeScript lint and dead codeeslint flat config with complexity, depth, function length and --max-warnings; tsc with noUnusedLocals and noUnusedParametersbaseline/eslint.config.js, baseline/tsconfig.base.json
Size and complexityper-module statement budgets that only go downscripts/budget.py, scripts/check_size.py in semsynth
Versionsone script fails when README, docs and packages disagreescripts/check_versions.py
Dependenciesa lock file in CI (uv sync --locked, npm ci); monthly grouped Dependabot; a weekly job that installs the newest of everythingsemsynth .github/workflows/canary.yml
Agent notesAGENTS.md of at most 30 lines; CLAUDE.md containing @AGENTS.mdbaseline/AGENTS.template.md

Two tiers keep this affordable. New code takes the strict settings. Legacy code takes the curated settings, with today's violations recorded as an ignore list or a warning count that may only shrink.

Left out on purpose: dead-code scanners such as vulture and knip, and mutation testing. ruff's unused-name and unused-argument rules and tsc's unused flags find most of what they would, and the rest is found by running vulture once by hand on a legacy project to seed a deletion list.

Pins to linked-codebook are the one dependency Dependabot cannot follow, because they are URLs. The semsynth canary job compares its pin with the latest release and warns; copy that step into other projects that depend on a release.