Skip to Content

Changelog

A reverse-chronological record of every shipped change that touches business-logic code or user-facing behaviour. Each entry is authored by the developer (with the docs-update skill’s help) and reviewed in the same PR as the code change.

See the docs-automation spec  for how this page is maintained, and the covers: / owns: convention for how /business-logic/ pages declare which code they document.

2026-05-21 — Docs automation shipped: docs-update skill + safety nets

Three pieces of tooling that keep /business-logic/ pages in sync with the code they document, plus a deterministic safety net so drift can’t slip through:

  • docs-update Claude Code skill (invoke via /docs-update or npm run docs:update) — reads your branch diff, classifies touched files via covers: / owns: frontmatter, proposes doc edits and a changelog entry into your working tree for review. Never commits, never writes outside docs/.
  • covers: / owns: frontmatter convention on every /business-logic/ page + npm run docs:lint-covers running on every CI PR. See the convention page for details.
  • Pre-push git hook + GitHub Actions safety nets: a deterministic path-overlap check fires both locally and on PRs. Business-logic changes without doc updates are flagged. The PR-title check posts a non-blocking sticky comment if no Jira ref is found.

Recognises Jira refs from both TUN- (main IBA backend) and TMA- (mobile app) projects by default; adding a third project is a one-line config change in docs/.docs-update.config.json.

  • Jira: [ticket?]
  • PR: [#?]

Last updated on