メニュー
Audit docs/* and root markdown for staleness. Checks `last_verified` headers against git mtime, validates Python code examples parse, checks cross-reference links resolve. Use monthly, before release, or after any large refactor.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/backblaze-labs/genblaze --skill verify-docsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Prepare a wave-level genblaze release — scope version bumps and dependency-floor drift with tools/prepare_release.py, apply them, gate with make pre-release, and open a release PR. Cannot tag or publish. Use before cutting a new CHANGELOG wave (as opposed to /release-check, which gates one already-decided package version).
Pre-release gate for one genblaze package — version bump, tests, lint, typecheck, CHANGELOG entry, entry-point sanity. Use before creating a GitHub Release (which triggers the PyPI publish workflow in .github/workflows/release.yml).
Scaffold a new genblaze provider connector package with all required files, tests, and entry points by analyzing existing connectors for conventions.
SOC 職業分類に基づく
| name | verify-docs |
| description | Audit docs/* and root markdown for staleness. Checks `last_verified` headers against git mtime, validates Python code examples parse, checks cross-reference links resolve. Use monthly, before release, or after any large refactor. |
| allowed-tools | Read Grep Glob Bash(git log:*) Bash(python3:*) |
Run the four checks below and produce a single report. Do NOT auto-fix — surface findings for human review (stale docs usually need a human to decide whether behavior is still accurate).
last_verified stampsEvery canonical doc in this repo carries <!-- last_verified: YYYY-MM-DD --> near the top.
README.md, ARCHITECTURE.md, AGENTS.md, CLAUDE.md, CONTRIBUTING.md,
docs/**/*.md.docs/dev-workflows.md.Owning-module lookup (from docs/dev-workflows.md):
| Doc | Owning module |
|---|---|
docs/features/pipeline.md | libs/core/genblaze_core/pipeline/ |
docs/features/provider-system.md | libs/core/genblaze_core/providers/ |
docs/features/media-embedding.md | libs/core/genblaze_core/media/ |
docs/features/object-storage.md | libs/core/genblaze_core/storage/ + libs/connectors/s3/ |
docs/features/parquet-sink.md | libs/core/genblaze_core/sinks/ |
docs/features/manifest-provenance.md | libs/core/genblaze_core/canonical/ + libs/core/genblaze_core/models/manifest.py |
docs/features/cli.md | cli/ |
ARCHITECTURE.md | whole repo — use root mtime |
docs/app-workflows.md | libs/core/ |
docs/dev-workflows.md | Makefile + .github/workflows/ |
Use git log -1 --format=%cs -- <path> to get last-touched date for a module.
Every Python fenced block in docs/features/*.md should at minimum be parseable.
python ... ), write to a temp file and run
python3 -c "import ast; ast.parse(open(p).read())".\[.+?\]\(\./.+?\), \[.+?\]\(\.\./.+?\),
\[.+?\]\(docs/.+?\).ARCHITECTURE.md has a "Canonical Files" section mapping concepts to paths. Confirm each path
listed there exists. Flag any libs/core/genblaze_core/... reference that no longer resolves
(a common rot pattern after refactors).
## Docs Audit — YYYY-MM-DD
### P1 — Stale `last_verified`
- docs/features/pipeline.md — stamp 2026-01-10, module last touched 2026-03-22
### P2 — Broken example syntax
- docs/features/webhooks.md — block 3: SyntaxError at line N
### P3 — Broken cross-links
- README.md → docs/features/queue-integration.md: target not found
### P4 — Missing canonical file
- ARCHITECTURE.md references libs/core/genblaze_core/old_module.py: not present