skills.rest
shuddl
shuddlCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

keep-ops-record-reconciled-with-deploys

Reconciles ops documentation claims with actual deployment and provisioning state after world-changing actions.

Updated Jul 9, 2026
Search Tags:#documentation#deployment#drift detection#wrangler#reconciliation#git grep#ops record
One-click install
npx skills add https://github.com/shuddl/shuddl-os --skill keep-ops-record-reconciled-with-deploys-shuddl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: keep-ops-record-reconciled-with-deploys
Source: https://github.com/shuddl/shuddl-os/tree/main/.claude/skills/keep-ops-record-reconciled-with-deploys
Command: npx skills add https://github.com/shuddl/shuddl-os --skill keep-ops-record-reconciled-with-deploys-shuddl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After provisioning, deploying, binding secrets, or taking backups, ops documentation often keeps asserting the old world — README files saying "nothing is deployed" while production is live — causing maintainers to treat live environments as inert and make dangerous mistakes. ## Core Features & Use Cases - Same-session supersession sweep: Runs a git grep across all tracked markdown and wrangler.toml files for stale phrases like "not provisioned", "nothing is deployed", and "placeholder" immediately after any world-changing action. - In-place supersession discipline: Replaces stale claims with strikethrough plus dated corrections and evidence pointers, preserving history instead of rewriting it. - Hold-row and config-comment hygiene: Flips BLOCKED hold rows with proof commands and fixes wrangler.toml comments that call real provisioned IDs placeholders. - Use Case: After deploying five workers and recording a passing preflight, sweep the repo so PROJECT-STATE.md, README.md, and runbooks stop claiming production does not exist. ## Quick Start After any deploy or provisioning action, ask the AI to run the ops-record reconciliation sweep across all tracked markdown and wrangler files and supersede any stale claims in place.

Frequently Asked Questions about keep-ops-record-reconciled-with-deploys

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep deployment documentation in sync after provisioning infrastructure?▼

Run a same-session sweep with git grep for stale phrases like "not provisioned" or "nothing is deployed" across all tracked markdown and wrangler.toml files, then supersede each hit in place with a strikethrough, date, and evidence pointer.

What is a supersession sweep in ops documentation?▼

A supersession sweep is a repo-wide search for claims contradicted by a recent world-changing action, followed by in-place corrections that preserve history. It covers every tracked markdown file, not just docs/ops, because root-level files like README.md are the most-read and least-updated.

Why should stale ops claims be struck through instead of deleted?▼

Strikethrough with a dated note preserves the audit trail and shows readers what changed and when. Deleting history rewrites the record, which violates the append-only documentation discipline this workflow enforces.

When should I run a documentation reconciliation sweep?▼

Run it immediately after provisioning, deploying, binding secrets, taking backups, or changing DNS and routing, and at every work-package exit or close-out. Also run it when editing a wrangler.toml ID whose comment describes it as a placeholder.

Why is under-warning drift in ops docs dangerous?▼

When docs claim nothing is live while production answers, maintainers treat prod-targeting actions like seeds, replays, and secret rotations as inert. That false sense of safety leads to accidental changes against a live environment.

Related Skills

Explore More Software Engineering Skills→
borealBytesborealBytes
7

release-openclaw-ci

Automate OpenClaw release validation, secret preflight, and failure triage.

Community
Advanced
alo-expalo-exp
6

gsd-validate

Validate code against SPEC.md and REQUIREMENTS.md to produce a PASS/FAIL report.

Official
Advanced
PostHogPostHog
713

signals-scout-feature-flags

Detects feature flag evaluation cliffs, ghost flags, distribution shifts, and flag debt in PostHog.

Official
Advanced
WhaleylawWhaleylaw

infrastructure-as-code-specialist

Manages cloud infrastructure declaratively with Terraform and Pulumi across GCP, AWS, Azure.

Community
Advanced