posthog/ai-plugin

context-layer-consolidation

Keep the context wiki coherent using the deterministic lint report queue

ソースを見る
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Context layer consolidation

Start with scripts/lint --report. Work the queue on the current dream branch.

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 commit message.

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

同じリポジトリから

関連する Skills

すべての Skills
posthog
公式

instrument-product-analytics

- Add PostHog product analytics events to track user behavior. Use after implementing new features or reviewing PRs to ensure meaningful user actions are captured. Also handles initial PostHog SDK setup if not yet installed.

導入数
1
GitHub Stars
81
更新日
9月10日
posthog
公式

auditing-endpoints

Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks "what endpoints can I clean up?", "are any of my endpoints broken?", "which materialised versions are still being called?", or wants a one-shot cleanup pass over the Endpoints product. Produces a prioritised report grouped by issue type, with recommended actions but does not modify anything without explicit confirmation.

導入数
1
GitHub Stars
81
更新日
9月10日
posthog
公式

authoring-data-quality-checks

Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Use when asked to test a model, validate a view, check for nulls or duplicates, add data quality checks, find out why a number looks wrong, or judge whether a warehouse table is trustworthy before using it in an analysis. To describe what data means (metrics, certifications

導入数
1
GitHub Stars
81
更新日
9月10日
posthog
公式

authoring-log-alerts

Author useful, low-noise log alerts on services in a PostHog project. Use when the user asks to set up alerts for their logs, suggest alerts they should add, or evaluate whether a service is worth monitoring. Covers service triage, baseline characterisation, threshold drafting, back-testing via simulate, and shipping with a notification destination.

導入数
1
GitHub Stars
81
更新日
9月10日