メニュー
Use when the marketing website may be stale. Discovers commits since the last website update, re-runs the source-extraction script, and updates website/ content so that generated pages match the current README, docs, and spec.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the repository may have drifted out of conformance with OSS_SPEC.md. Runs `oss-spec validate .`, walks the violations, and fixes each one so the self-conformance test keeps passing.
Use when prompts under prompts/ may be stale. Discovers changes to OSS_SPEC.md, the validator, manifest enums, and the ai/fix glue since the last run, and rewrites the affected prompt templates so they stay aligned with their sources of truth.
Use when files under docs/ may be stale. Discovers commits since the last docs update, maps changed source files to affected conceptual documentation, and brings docs/*.md back into sync with the implementation.
Use when README.md may be stale. Discovers commits since the last README update, identifies what changed (CLI flags, subcommands, §19 rules, supported languages, spec version), and updates the affected README sections.
Use when OSS_SPEC.md has been edited. Bumps the spec version field, propagates the new mandate through validate.rs, tests, templates, docs, README, AGENTS.md, and the self-conformance test.
Use when you want to bring every drift-prone artifact in the repo back into sync. Dispatches to all individual update-* skills in the correct order, aggregates their results, and leaves a single combined PR ready to review.
| name | update-website |
| description | Use when the marketing website may be stale. Discovers commits since the last website update, re-runs the source-extraction script, and updates website/ content so that generated pages match the current README, docs, and spec. |
The website/ directory contains the marketing site for oss-spec. Per §11.2 of OSS_SPEC.md, its source-derived content (hero copy, feature lists, version strings) must not be authored twice — it is extracted from README.md, docs/, and OSS_SPEC.md by a script, then rendered by the website build.
.agent/skills/update-website/.last-updated contains the git commit hash from the last successful run. Empty means "never run" — fall back to the initial commit.
Read the baseline:
BASELINE=$(cat .agent/skills/update-website/.last-updated)
Diff sources of truth against the baseline:
git log --oneline "$BASELINE"..HEAD -- README.md docs/ OSS_SPEC.md
git diff --name-only "$BASELINE"..HEAD -- README.md docs/ OSS_SPEC.md
If anything changed, re-run the source-extraction script:
make website
Read the generated pages and confirm nothing committed under website/src/generated/ disagrees with the current sources.
| Changed file | Effect on website |
|---|---|
README.md hero / quick start | Home page feature summary |
README.md Usage table | CLI reference page |
docs/getting-started.md | "Getting started" page |
docs/architecture.md | Architecture page |
OSS_SPEC.md front-matter version: | Version badge on the home page |
Read baseline and diff sources of truth
Run make website to regenerate extracted content
Review the diff under website/src/generated/ and commit the changes
Build the website locally (make website-dev) and smoke-test the home page
Confirm the §11.2 staleness CI check would pass
Run oss-spec validate .
Write the new baseline:
git rev-parse HEAD > .agent/skills/update-website/.last-updated
.last-updated was rewritten.