ckb/.agents/skills/ckb-lint/references/edge-cases.md
Michał Kopeć 7863115b74 Template 1.10.0: slim skills, review fixes, docs/, tests, retrieval script
- Skills: descriptions cut to routing-hint length (1925w -> 840w), Trigger
  phrases removed, Purpose collapsed, Edge cases moved to references/.
- Rule B names the decisions-log exception; "Sync the wiki" trigger dropped;
  reserved sections "Four" -> "Three"; directory contract adds ckb.yaml,
  docs/, tests/.
- MANUAL/CHANGELOG/OPENSPEC (EN+PL) moved to docs/; template ADRs D-0001 and
  D-0002 restored from 0c06cb6 into docs/decisions/; referrers repointed.
- ckb-retrieve: rank fusion moved into scripts/retrieve_candidates.py;
  Purpose states the one write it owns (query-gaps).
- tests/: fixture KB, golden JSON, smoke.sh.
- Scaffold: overview.md describes content not schema; graph/index.md names
  base skills only; query-gaps.md loses its self-rotting freshness window.
- README/MANUAL/OPENSPEC/CHANGELOG ghost-writer pass in both languages.
- VERSION 1.9.0 -> 1.10.0.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-09-24 20:45:09 +02:00

2.2 KiB

ckb-lint — edge cases

Reference material for the ckb-lint skill. Read when a run hits an unusual situation the main steps don't cover.

  • Wiki is empty or near-empty — report that there's little to lint yet; don't fabricate findings to look thorough. A total findings: 0 report is a valid outcome; say so plainly rather than hunting for something to say.
  • A page's frontmatter is unparseable (not just missing type, but invalid YAML) — the script reports it under conformance and skips it in the later checks rather than reasoning from a half-parsed page. Surface it prominently and fix the frontmatter first; a page can't be judged stale, orphaned, or archivable until it parses.
  • Retention sweep would archive a page that's clearly still in active use (e.g. linked from a very recent workload/ entry) — flag it for the user to confirm rather than auto-archiving; recency of use can override a stale last_updated/retention combination.
  • Supersession is ambiguous (two pages disagree and neither is clearly newer/better corroborated) — report the conflict rather than guessing which one wins.
  • Repeated run with nothing changed since the last lint — produces the same report each time (pass --today to pin the date if you need a byte-identical one); don't invent variation just to seem active.
  • A changed fingerprint and a diverged crux quote on the same page — one incident, not two. The source was edited; fix the page once against the new content and re-stamp both the digest and the quote together.
  • Every page in the wiki lacks fingerprints — a wiki built before this convention. Don't stamp them all in one pass; that produces a tree of digests attesting to nothing anyone verified. Report the count, and backfill as pages are touched for other reasons.
  • The script errors out or isn't runnable (no Python 3, unreadable tree) — say so and fall back to working the numbered checks by hand rather than reporting a clean bill of health you didn't actually verify.

Licensed under the Apache License, Version 2.0 — see LICENSE at the repository root, or http://www.apache.org/licenses/LICENSE-2.0.