context-layer-consolidation

Consolidate context wiki Markdown pages using a deterministic lint report queue.

713|118|Updated Aug 11, 2020
One-click install
npx skills add https://github.com/PostHog/posthog-foss --skill context-layer-consolidation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-layer-consolidation
Source: https://github.com/PostHog/posthog-foss/tree/main/products/context_layer/skills/context-layer-consolidation
Command: npx skills add https://github.com/PostHog/posthog-foss --skill context-layer-consolidation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Context wikis accumulate unsupported synthesis, expired priorities, duplicate pages, and broken links over time, making them unreliable as a knowledge source. This Skill provides a bounded, evidence-led workflow to clean up the wiki using a deterministic lint report.

Core Features & Use Cases

  • Lint-driven cleanup queue: Start from scripts/lint --report and work the reported issues on the current dream branch.
  • Content hygiene rules: Remove unsupported synthesis, expire stale priorities, mark superseded decisions, merge near-duplicates, and repair ghost links.
  • Strict edit boundaries: Only sourced Markdown under org/, areas/, decisions/, and Space pages may be edited; structural failures are reported back for server-side repair.
  • Use Case: A team maintaining a PostHog context layer wiki runs this Skill each cycle to keep decisions, areas, and org pages coherent without touching generated indexes or scripts.

Quick Start

Run the context layer consolidation skill to work through the lint report queue and clean up the context wiki on the current dream branch.

Frequently Asked Questions about context-layer-consolidation

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

FAQPage Schema
How do I clean up a context wiki with lint reports?

Run scripts/lint --report to get the issue queue, then work through it on the current dream branch. After editing, run scripts/lint again to verify the fixes.

What files can the context layer consolidation skill edit?

It only edits sourced Markdown content under org/, areas/, decisions/, and existing Space pages. It never edits repository instructions, generated indexes, or scripts; structural failures are reported in the run summary for the server to repair.

How are outdated decisions handled in a context wiki?

Replaced decisions are marked as superseded with a link to their replacement. Expired priorities are removed unless historically significant, in which case they are marked with status: historical.

What are the limitations of lint-driven wiki consolidation?

It cannot fix structural failures itself; those must be reported for server-side repair. Disagreements are only resolved with evidence, otherwise they remain explicit, and every deletion must be named in the commit message.

How do I handle duplicate pages in a context wiki?

Near-duplicate pages are merged into a single page, leaving a wikilink from the old subject so existing references continue to resolve.