ワンクリックで
update-readme
Update README.md with the latest API coverage data from the api-coverage skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Update README.md with the latest API coverage data from the api-coverage skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate AWS API coverage reports comparing winterbaume implementations against official AWS API models, plus Terraform converter coverage at the resource-type and per-attribute levels.
Use when the vendored AWS Smithy models under vendor/api-models-aws change, or when API coverage, README service tables, TODO unimplemented-service lists, generated model/wire files, or service dossiers need to be reconciled with the current Smithy checkout.
Implement or enhance an AWS service in winterbaume — creates a new crate from a stub or adds missing operations to an existing crate. Targets moto API coverage parity.
Port moto's Python test cases for a given AWS service to winterbaume Rust integration tests. Reads moto tests from the moto GitHub repository, translates to aws-sdk-rust + MockAws style, and appends to existing integration_test.rs.
Check whether a service crate passes the publication quality gate, then fix all failures. Reads the crate's source files, runs build/clippy/test, reports pass/fail for each gate check, creates a TODO list of failures, and works through them until the crate passes.
Generate a new AWS service dossier under .agents/docs/services or enhance an existing service dossier with Smithy-derived operation/resource facts, official AWS documentation research, concrete usage scenarios, and durable Winterbaume LTM lessons.
| name | update-readme |
| description | Update README.md with the latest API coverage data from the api-coverage skill. |
| user_invocable | true |
Update the "Supported Services" section in the workspace README.md, regenerate per-service crate README.md files, and sync the user-facing docs/ site with the latest API coverage data.
Regenerate the coverage report by running:
python3 .agents/skills/api-coverage/scripts/generate_coverage.py
Update README.md files and docs/ by running:
python3 .agents/skills/update-readme/scripts/update_readme.py
This parses .agents/docs/API_COVERAGE.md, rewrites the Supported Services table in the workspace README.md (merging fully-implemented services and stub-only services into one sorted table), regenerates crates/winterbaume-*/README.md files, regenerates the two Terraform coverage reports under .agents/docs/TERRAFORM_*_COVERAGE.md and the user-facing docs/reference/terraform.md, and updates the rest of the docs/ directory.
.agents/docs/API_COVERAGE.mdREADME.md and replaces the entire ## Supported Services section (including the old ### Stub Services subsection if present) up to the next ## headingREADME.mdREADME.md with a generated coverage summary that includes the service name, AWS model, protocol, winterbaume coverage, moto coverage, floci coverage, kumo coverage, fakecloud coverage, coverage report date, an explicit list of implemented APIs, and a collapsible list of APIs not yet implemented (with notes where moto, floci, kumo, or fakecloud implement the missing operation)README.md; currently this includes ## Current Network Resource Stub Semantics when present in .agents/docs/services/<model-slug>.md--no-docs is passed):
generate_terraform_resource_coverage.py and generate_terraform_converter_coverage.py from the api-coverage skill ( unless --no-terraform is passed ) so the two .agents/docs/TERRAFORM_*_COVERAGE.md reports are fresh, then rewrites docs/reference/terraform.md from those reports — including per-service resource-type coverage, per-resource attribute coverage, and the overall rating distributiondocs/reference/services.md with the same merged services table (no crate links, plain display name) and a footer linking to the Terraform coverage page with the live distinct-resource-type countdocs/index.md hero feature blockcrates/winterbaume-*/README.md (excluding infrastructure crates) into docs/services/<slug>.md, stripping crate-only guidance such as the package/workspace boilerplate, legal notice, and generated-source notes so the service docs stay focused on the service surface (no Node.js required)The script maintains a mapping from crate names to human-readable service names and protocol identifiers. When adding a new service, update CRATE_DISPLAY_INFO in .agents/skills/update-readme/scripts/update_readme.py.
| Flag | Default | Description |
|---|---|---|
--coverage PATH | .agents/docs/API_COVERAGE.md | Path to the coverage report |
--readme PATH | README.md | Path to the workspace README |
--crates-dir PATH | crates | Path to the crates directory |
--docs-dir PATH | docs | Path to the docs directory |
--no-docs | off | Skip all docs/ updates |
--no-terraform | off | Skip regenerating Terraform coverage reports and docs/reference/terraform.md (still runs when --no-docs is not set, by default) |