context-layer-health-check

Reviews context wiki quality using wiki-miss signals from git merge logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After deterministic consolidation of a context wiki, quality issues like contradictory claims, stale priorities, and near-duplicate pages can accumulate undetected. This Skill performs a semantic review pass to surface and fix those problems.

Core Features & Use Cases

  • Signal-driven review: Reads recent wiki-miss: lines from git log --merges to prioritize which areas of the wiki need attention.
  • Semantic quality checks: Detects contradictory active claims, unsupported conclusions, repeated low-value activity, stale priorities, near-duplicate subjects, and concepts lacking an owning page.
  • Safe conflict handling: Fixes issues supported by evidence, marks unresolved conflicts as **Disagreement:** entries, and records remaining work in a run summary.
  • Use Case: After a batch of automated wiki consolidations, run this health check to catch contradictions and gaps the deterministic tooling cannot detect, then verify with scripts/lint and scripts/lint --report.

Quick Start

Run a health check on the context wiki using recent wiki-miss signals from the git merge history and fix any supported issues.

Frequently Asked Questions about context-layer-health-check

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

FAQPage Schema
How do I check the quality of a context wiki after consolidation?

Run this health check, which reads recent wiki-miss lines from git log --merges to prioritize review areas. It flags contradictory claims, unsupported conclusions, and stale priorities, then finishes with scripts/lint and scripts/lint --report for validation.

What are wiki-miss lines in git log used for?

Wiki-miss lines in merge commits record cases where the deterministic consolidation could not resolve something. They serve as the priority signal telling the reviewer which parts of the wiki most need semantic attention.

How are unresolved contradictions in the wiki handled?

Contradictions that lack sufficient evidence to resolve are left in place as **Disagreement:** markers rather than being arbitrarily fixed. Remaining unresolved work is recorded in the run summary for later follow-up.

What files should not be edited during a wiki health check?

Do not edit AGENTS.md, CLAUDE.md, generated indexes, anything under scripts/, or Space paths. The server owns the wiki structure and tooling, so the review only touches content pages.

When is a semantic wiki review needed instead of linting alone?

Lint scripts catch structural and formatting issues but cannot detect contradictory claims, unsupported conclusions, or near-duplicate subjects. A semantic review is needed after consolidation to catch these content-level problems.