Files
chemenu/docs/reference/README.md
T
torbenandClaude Opus 5.5 070cae6aad
CI / verify (push) Successful in 6m10s
CI / pwsh (push) Successful in 1m59s
Release / release (push) Successful in 34s
feat: docs reference generates a skill catalogue and a page-type reference under docs/reference/ from the shipped defaults, checked and written in the origin repo only (#189)
Files changed:
- CHANGES.md
- README.md
- VERSION
- docs/reference/README.md
- docs/reference/commands/README.md
- docs/reference/commands/types-instructions-and-docs.md
- docs/reference/page-types.md
- docs/reference/skills.md
- instructions/dev/doc-pull-through.md
- tools/CONTRACT.md
- tools/README.md
- tools/chemenu/commands/docs_verify.py
- tools/chemenu/reference_doc.py
- tools/chemenu/tests/test_reference_doc.py

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SnAJ7Z3CpVD3PRbN73QtU2
2026-10-06 22:10:09 +02:00

1.1 KiB

Reference

Lookup pages: the command surface, exit codes and gates, the skill catalogue, the page types. A reference page describes what is, not how to use it or why it is so - and wherever a source for it exists in the code, it is generated from that source and checked against it rather than written by hand.

  • Command reference - every wikitool command, one page per group, generated from the same records as tools/wikitool <command> -h.
  • Exit codes and gates - which commands can stop and wait for a person, and why.
  • Skill catalogue - the skills the stack ships, what each does and which requests start it, generated from their SKILL.md.
  • Page types - every page type the stack ships for kb/, its subtypes, where its pages are written and its required fields, generated from the type-specs.

The last two describe the stack's shipped defaults, which an instance may change or extend; tools/wikitool instructions list and tools/wikitool types describe <type> show what one instance has.