Context Layer Consolidation

From the author

Keep the context wiki coherent using the deterministic lint report queue

— the description by PostHog

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Context layer consolidation provides a systematic procedure for keeping a wiki coherent. By utilizing a deterministic lint report queue, the agent processes documentation under specific directories to ensure consistency, resolve redundancies, and manage the lifecycle of decisions and priorities before publication.

What it does

Processes lint reports to identify documentation issues.
Consolidates and merges near-duplicate wiki pages.
Updates the status of decisions and priorities.
Repairs or documents broken links and splits oversized content.
Summarizes all deletions for inclusion in commit messages.

When to use it

When preparing a wiki for publication.
When documentation becomes fragmented or contains redundant information.
When managing the lifecycle of project decisions and priorities.
When linting reports indicate structural or content inconsistencies.

Advantages

Ensures documentation remains evidence-led and coherent.
Provides a clear audit trail of changes via run summaries.
Maintains a structured approach to wiki maintenance.
Prevents the accumulation of expired or unsupported content.

Usage examples

“Run the context consolidation workflow.”: The agent executes the lint script, processes the report queue, cleans up the specified wiki directories, and generates a summary of changes.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/posthog/context-layer-consolidation/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip context-layer-consolidation.zip -d .agents/skills

Documentation by PostHog

Start with scripts/lint --report. Work the queue in the mounted wiki before the dream publisher creates its branch and commit.

Only edit sourced Markdown content under org/, areas/, decisions/, and existing Space pages. Never edit repository instructions, generated indexes, or scripts/; report structural failures in the run summary for the server to repair.

Remove unsupported synthesis.
Remove expired priorities unless historically significant; mark those status: historical.
Mark replaced decisions superseded and link their replacement.
Merge near-duplicates and leave a wikilink from the old subject.
Resolve disagreements only with evidence; leave the rest explicit.
Repair or intentionally retain ghost links, add sources, and split oversized pages.
Name every deletion in the run summary. The dream publisher includes it in the commit message.

Keep this bounded and evidence-led. Run scripts/lint after editing.

Files

ATTRIBUTION.mdAdded by AutoGineer873 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md1.1 KiB

SKILL.md