Documentation Update

---
name: documentation-update
description: |
  Sweep documentation after code changes: find outdated references,
  update all affected docs, commit.

  Use when: "документация", "обнови доки", "docs sweep", "sweep docs",
  "проверь доки после изменений", "update docs after changes"
---

# Docs Sweep

Update project documentation to match current code.

Правишь любой `.md` — сперва определи ЖАНР по скиллу `documentation-writing` и открой гайд
этого жанра в его `references/`: закон, справочник, инструкция, разбор, агент. Своей
структуры не выдумывай.

## Step 1: What Changed

Look at the current conversation: what files were modified, what behavior changed,
what was added/removed/renamed. If no conversation context — use `git diff`.

## Step 2: Read All Docs

Read every file in `.claude/skills/project-knowledge/references/*.md`, `README.md`, `CLAUDE.md`.
Read each file fully — no skipping sections.

## Step 3: Find and Fix Stale References

For each change from Step 1, search ALL doc files for references to old values.
When fixing a value in one doc, grep the old value across ALL docs — same fact
often lives in multiple files.

Also verify:
- **File map matches disk:** `ls` each directory in the file map, check both directions
  (every doc entry exists on disk, every file on disk is in the doc)
- **Numbers are correct:** counts (test files, rules, hints), versions, thresholds —
  verify against actual code
- **Descriptions match behavior:** if a doc says "does X", confirm the code still does X

## Step 4: Final Check

Grep all old values one more time across all docs. Zero hits = done.

## Step 5: Commit

```
git add <changed doc files>
git commit -m "docs: sync documentation with {brief description}"
```