Context Layer Consolidation

作者 PostHog469d1773e9cb無授權條款收錄於 2026年10月8日更新於 2026年10月8日

Keep the context wiki coherent using the deterministic lint report queue

AI 產生的概覽

透過處理 lint 報告佇列來維護情境 wiki,修正連結、重複內容與缺乏依據的內容。

功能
此技能引導代理在工作分支上整併 Markdown 情境 wiki。它從確定性的 lint 報告開始,接著編輯 org/、areas/、decisions/ 及現有 Space 頁面中有來源的內容,移除缺乏依據的綜合內容、標記過期優先事項與被取代的決策、合併近似重複項目,並修復或刻意保留幽靈連結。最後重新執行 lint 檢查,並在提交訊息中列出每一處刪除。
適用情境
適用於情境 wiki 出現內容漂移、需要清理 lint 報告佇列的情況。適合定期維護,要求編輯有憑有據且範圍受限。
執行需求
需要一個具備所述目錄結構的情境 wiki 儲存庫,以及以 scripts/lint 方式呼叫的 lint 指令碼;此技能本身不附帶指令碼,僅為說明文件。它假定已有工作分支與提交權限。

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.

來源與署名

來源:PostHog/ai-plugin位於skills/context-layer-consolidation提交469d177

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 PostHog/ai-plugin 的技能

Writing Simplified Technical English

PostHog

套用 ASD-STE100 簡化技術英語規則,讓代理撰寫的文字語意明確、方便執行。

Writing & Content2026年10月8日

Working With Task Comments

PostHog

透過 PostHog MCP exec 調度器讀取並解讀 PostHog 任務、成品和畫布上的留言。

Productivity & Workflow2026年10月8日

Working With Skills

PostHog

指導代理使用 PostHog 的 skill-* MCP 工具來探索、讀取、建立、更新與重構技能。

AI & Agents2026年10月8日

Working With Scouts

PostHog

說明如何把監看工作委派給 PostHog Signals 偵察代理、處理其回報,並長期調校整個代理團隊的操作手冊。

AI & Agents2026年10月8日

Validating And Publishing Canvases

PostHog

Validate and publish a canvas source project safely: the source-project shape, declared capabilities, reading the current version pointer, iterating on validation diagnostics, guarded publishing with expected_current_version_id, staging a draft build and promoting it, waiting out the queued build, and recovering from a 409 version_conflict or a 429 capacity limit without overwriting concurrent work. Use whenever a canvas edit is ready to save, a draft build is wanted, a canvas publish or build returns diagnostics or a conflict, or a task needs to understand canvas version history.

待分類2026年10月8日

Understanding Billing Usage

PostHog

Explains PostHog billing usage and spend from the customer's visible Billing MCP tools. Use when the user asks why usage or spend is high, which product or project is driving usage, what a usage type means, how to reduce usage, what changed over time, why they got a usage change alert, or whether a spike/drop alert was real or noisy. Also use before product-specific analytics skills when the user names a billable PostHog product metric such as events, recordings, feature flag requests, exceptions, survey responses, synced rows, logs, AI events, AI credits, or Inbox credits. Starts from Billing usage/spend tools, then routes to customer-visible product MCP surfaces for deeper investigation.

待分類2026年10月8日