context-cleanup-steward

Reconcile repo docs, code, routes, Notion tickets, Drive context, and Stitch references.

Updated Apr 2, 2026

Search Tags:#documentation #cleanup #release #notion #drift #drive

Ready to run

npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill context-cleanup-steward

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context-cleanup-steward
Source: https://github.com/oteroweb/OWFINANCE2026/tree/main/.agents/skills/context-cleanup-steward
Command: npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill context-cleanup-steward

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates and de-drifts OWFINANCE repo docs by aligning code, Notion metadata, Drive context, and route reality to reduce confusion and stale context.

Core Features & Use Cases

Archive before delete and preserve the source of truth.
Align Notion tickets with current code and docs; update Drive context indexes.
Quick remediation when drift is detected in documentation or references.

Quick Start

Run the cleanup steward after a release validation to reconcile and archive drifted docs.

Frequently Asked Questions about context-cleanup-steward

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

FAQPage Schema

How do I reconcile documentation drift between my repo and Notion tickets?▼

To reconcile documentation drift, align Notion ticket metadata with current runtime code, repo docs, and route reality. You apply a cleanup workflow after deployment validation or closing ticket batches to update indexes and resolve conflicting references.

When should I archive drifted repository documents instead of deleting them?▼

Archive drifted repository documents before deleting them to preserve the source of truth. Run this consolidation process when the workspace accumulates duplicate or conflicting documents, ensuring Notion tickets and Drive context remain accurate without losing history.

What is the best way to clean up stale Drive context and UI references after a release?▼

The best way to clean up stale Drive context and UI references is to run a post-deployment validation cleanup. This aligns Stitch references used by UI work with runtime routes and updates Drive context indexes to eliminate stale context.

Does the documentation cleanup process preserve source-of-truth ownership when drift is unresolved?▼

Yes, the documentation cleanup process preserves source-of-truth ownership. When drift cannot be fully resolved, it archives the conflicting documents before deletion and updates Notion tickets and Drive indexes to reflect the current validated state.

How to update Notion ticket metadata to align with current code and route reality?▼

To update Notion ticket metadata, run a cleanup steward workflow after closing a batch of tickets. This reduces drift by comparing ticket details against runtime code and route reality, then updating the metadata and Drive context accordingly.

Why does documentation drift occur between code, Notion, and Drive context?▼

Documentation drift occurs because code, Notion metadata, and Drive context evolve independently during development. Applying a consolidation workflow after deployment validation detects and remediates this drift by aligning all references to the current route reality.