Skip to content

0.0.37 — Skills for Claude sessions, a quality register, and tests on shot editing

Choose a tag to compare

@github-actions github-actions released this 26 Sep 08:45
· 13 commits to main since this release
7157b25

Under the hood: how Claude works on this app, and what it's now allowed to trust

Nothing changes on screen. This release makes the numbers behind the screen better guarded and
the way the app is built more reliable.

  • New tests on shot editing. Marking an edited shot Holed removes the shots after it; editing an
    earlier shot re-derives the later starts and stores the right strokes gained for every shot; a
    stroke-and-distance penalty always costs exactly two strokes whatever was typed. These were the
    behaviours the app relied on but never checked.
  • A quality gate on the course directory. A test now checks the committed course list itself:
    every course has one of the 32 counties and sits on the island, the share with a known hole count
    can't fall, and the known gaps (missing clubs, duplicate entries) are listed and must shrink. It
    found a fourth non-course on its first run.
  • A quality register (docs/quality.md): every feature's data confidence, its known issues,
    the test that pins it and the GitHub issue, so a problem a player could notice is never only in a
    chat. Filed from it: a scoring bug where a shot entered as 0 ft and not holed is scored as holed
    (#40), the directory's missing clubs and hole counts (#38), and the thin scratch benchmark (#39).
  • Skills for Claude Code sessions (.claude/skills/): /how explains an area with parallel
    read-only explorers and can critique it with independent reviewers; /verify runs the same
    checks as CI in one command and has a separate verifier check a subagent's claims; /brigade
    runs many subagents at once with one writer per file and a verifier on every change;
    /correct turns a correction into a permanent fix at the lowest level that can hold it. A
    CLAUDE.md points every session at them.
  • Where code lives is now a test too: logic in src/lib with a test beside it, pages and
    routes thin, data under src/lib/*/data, and counts of the exceptions that may only go down.