weave-docs
/weave-docs
Utrzymuje aktualność dokumentacji zmian w Weave: wylicza wpływ zmiany na dokumenty, stosuje go i sprawdza odchylenia.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 2
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 30.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Utrzymuje aktualność dokumentacji zmian w Weave: wylicza wpływ zmiany na dokumenty, stosuje go i sprawdza odchylenia.
Oryginalny opis (EN)
Documentation currency for Weave changes. Computes the documentation impact of a change from the documentation map, applies it, regenerates generated documents, and runs the offline drift audit (repository or change scope). Use at claim time, before the In Review gate, at milestone exit, and whenever documents or the map change.
Jak działa
- At claim time
- Before the In Review gate
- Periodic and milestone audits
- When documents are added or removed
Podgląd SKILL.md
---
name: weave-docs
description: Documentation currency for Weave changes. Computes the documentation impact of a change from the documentation map, applies it, regenerates generated documents, and runs the offline drift audit (repository or change scope). Use at claim time, before the In Review gate, at milestone exit, and whenever documents or the map change.
---
# Documentation impact and drift audit
Policy: `docs/development/documentation-currency.md`. Map:
`docs/development/documentation-map.md` (generated part from
`tools/weave_workflow/docmap.json`).
## At claim time
The `claim` command computes the impact list from the allowed paths and publishes it as
DOCS_IMPACT. Review it: add documents the map misses (with a reason) and never shorten it
without a recorded justification (`status: not-applicable`, `justification: ...`).
## Before the In Review gate
1. Apply every entry of the impact list. Use the `weave-docs-editor` subagent for larger
edits; it may not change normative semantics, provenance or expected-rejection fixtures.
2. Regenerate, never hand-edit, generated documents:
- `cd inventory-proof && python3 demo.py` (REPORT.md, ACTUAL_OUTPUT.txt and other outputs)
- `cd specification && python3 scripts/refresh_reference_pages.py` (rule catalogue,
conformance appendix)
- `cd agent-kit && python3 scripts/sync_skill_reference.py` (skill copy of `agent-kit/docs/weave.md`)
- `python3 -m tools.weave_workflow docs-map --write` (after editing `docmap.json`)
3. Update claims from tool output in the same change (test counts, state and edge counts,
diagnostic codes, commands, hashes). If a figure cannot be verified, say so in the
document instead of stating it.
4. If a boundary moved (something became implemented, or was narrowed), update the
specification's `status.rst`, `limitations.rst` and `design-history.rst` and every document
that stated the old boundary.
5. Run and publish the change-scope audit of the committed candidate, with the impact list
from the packet:
`python3 -m tools.weave_workflow docs-audit --publish <N> --apply`, adding `--impact <file>`
only to extend the claim's list or to mark entries `not-applicable` with a justification.
The audit always uses the claim's worktree, base revision and published DOCS_IMPACT list (it
refuses a shortened list or a different base). It publishes DOCS_AUDIT_RESULT (scope `change`, the head SHA, result, error count). On FAIL
the In Review gate stays closed and the transition adds `agent:docs-stale`.
6. Warnings about protected vocabulary need a reviewer to confirm that the new use carries
the specification's meaning.
## Periodic and milestone audits
Run `python3 -m tools.weave_workflow docs-audit` (repository scope) at the start of every
run and at milestone exit. Keep one `agent:managed` documentation-audit issue listing
residual drift. A milestone cannot exit while that issue lists drift in its scope.
## When documents are added or removed
Update `tools/weave_workflow/docmap.json` (managed, historical or generated lists, impact
rules, claims) and regenerate the map. Mark not-yet-existing or external paths in the
document with `<!-- docs-audit: planned ... -->` or `<!-- docs-audit: external ... -->`.
Wersje
W bazie nie ma innych skilli o nazwie weave-docs.
Migawka bazy z 13.11.2026 · wersja paczki ad4b0c3a9e62 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100weave
Pisze, sprawdza, przekształca, symuluje i testuje pliki .weave, używając prototypu sieci Petriego. - 100weave
Pomaga skonfigurować weave do scalania na poziomie encji, podglądać scalenia, ograniczać fałszywe konflikty Git i sprawdzać działanie merge drivera. - 90weave-instrument
Dodaje śledzenie Weave do agentów i aplikacji LLM w Pythonie lub TypeScript: wywołań modeli, narzędzi i tur agenta. - 100write-docs
Pisze dokumenty, opisy pull requestów i commity dla zmian w dokumentacji, ADR oraz opisów zmian. - 90weave-project
Prowadzi przebiegi rozwoju Weave na GitHubie: wybiera zadanie, przydziela etykiety, aktualizuje statusy i raportuje. - 100vibe-review-docs
Przegląda zmiany w dokumentacji, sprawdza pliki wejściowe, jakość changeloga i dryf pojęć w opisach.