Run contextlint over the project's structured Markdown and fix the violations it detects. Use this skill whenever the user asks to fix lint errors, clean up docs, repair broken Markdown links, or after bulk edits to documentation (especially AI-generated specs/ADRs) — even if they don't explicitly mention contextlint…
Analyze the impact of changing or deleting a Markdown document by leveraging contextlint's Context Graph. Use this skill whenever the user asks "what breaks if I change X?", "what depends on this doc?", "is it safe to delete this file?", or wants to plan a refactor / understand cross-doc dependencies — even if they…
Bootstrap contextlint into a repository. Use this skill whenever the user wants to set up, install, initialize, or configure contextlint — even if they only say "lint setup", "doc integrity check", or "set up Markdown linting" without naming contextlint by name. Detects the package manager (bun/npm/pnpm/yarn), scans…
Add a beta-only curated factory to terradartgooglebeta (filtered-fixture extraction, googlebeta override, wrap with provider pin). Use when a later provider pin introduces a new beta-only google type — the current pin's beta-only catalog is filled.
Add or update a curated Google Cloud factory via terradart wrap (schema.json, optional MM YAML, wrapper override, lint, regenerate). Use when extending terradartgoogle with a new google resource.
Run TerraDart's shared agent gate (docs consistency, analyze, tests, wrap --check, pubsub smoke). Use before claiming maintainer or agent work is complete.
Backfill example quickstarts for curated factories listed in tool/exampledebt.yaml — extend stacks, sync debt, and run terraform validate locally before PR.
Ship a TerraDart Wave release — curated factories, examples/docs debt, catalog counts, CHANGELOG, and agentverify. Use when landing multiple related google resources as one user-visible release.
After example backfill, wire orphan factories into sibling refs (SSL certs on proxies, health checks on backends) and run topology + terraform validate gates.
You are the weekly post-processor for TerraDart's schema-bump PR. You judge and repair; you NEVER merge. A separate workflow (bump-merge.yml) re-verifies your verdict mechanically and performs the merge.
You ship one curated-factory Wave per run from the curation backlog. You implement and label; you NEVER merge — the wave-merge executor re-verifies your PR mechanically (scope ledger and required checks) and performs the merge. Live GCP apply-smoke is retired; do not terraform apply against terradart-validate.