kamehadb: Skill for Claude Code

Document Wiki

Create or refresh the target repository's docs/llm/ from verified source code. This is the one-stop wiki workflow; do not hand the user off elsewhere.

Completion contract

An inventory of routes, files, or modules is baseline coverage, not deep feature documentation. A selected feature is complete only when its page explains current business behavior and its material claims are traceable to source or tests read in the current run. Mark [ ] an undocumented feature and [x] a feature verified against that evidence. Use [~] for either a verification limit (checks remain incomplete or required evidence is inaccessible; the page may be correct, so it is not a refresh candidate) or a confirmed content gap (completed checks prove a material omission or a claim that contradicts source; a refresh candidate). State which one and why; they are not equivalent. Never call unverified coverage current.

Task updates

When implementation calls this skill for an active task, use this procedure instead of the whole-wiki Workflow below. The task's scope selects its affected behavior automatically; no extra page-selection approval is needed. Standalone wiki requests use the Workflow and its selection gate.

1. If docs/llm/ is absent, return not-applicable without setup or wiki creation. Otherwise apply Workflow step 1's instruction preflight, without its missing-wiki setup, and read the index and relevant pages. Use approved scope, the diff, and the current impact map/caller trace to select changed behavior, including callers outside the diff. Inventory or document no neighboring feature and create no repository-wide overview.
2. Merge any task delta with ## Merge a task delta before other content edits, preserving its exact after-merge blocks. If a delta block itself needs correction, reconcile the delta and wiki together using source and approved decisions; unresolved conflicts stop the update. A merge marker alone never proves the merge is correct.
3. Read current source and relevant tests and use the evidence matrix and page template for the selected behavior. Refresh stale content and add missing task behavior to the smallest relevant page. If its domain has no page, create a scoped page and register its prefix per Workflow steps 7-8; source-established domain boundaries need no approval. Reuse existing IDs/prefixes, preserve unrelated content, and report unrelated gaps as optional suggestions. A new page documents this task's behavior, not its module's every feature.
4. Ask only for unresolved behavior, conflicting requirements/source, domain boundaries not established by evidence, missing access, or work beyond the task's scope. Missing evidence for required task behavior keeps the task incomplete; do not invent it or mark it complete with an open question.
5. Update Sources, index links, and retired IDs as applicable and run ## Verify the wiki. Report any legacy-link migration conflict or scope issue. Verify each changed claim against source and tests: a validator pass or an Evidence path alone does not prove behavior.
6. Return changed pages, covered behavior, checks, and blockers to the caller. Never archive, mark task progress, or change approval here; implementation and final review own those actions.