[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-cleaning-up-stale-feature-flags":3,"mdc-qadsmv-key":38,"related-org-posthog-cleaning-up-stale-feature-flags":714,"related-repo-posthog-cleaning-up-stale-feature-flags":887},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":33,"sourceUrl":36,"mdContent":37},"cleaning-up-stale-feature-flags","clean up stale PostHog feature flags","Identify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal workflows.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png",[12,16,17,20],{"name":13,"slug":14,"type":15},"Operations","operations","tag",{"name":9,"slug":8,"type":15},{"name":18,"slug":19,"type":15},"Feature Flags","feature-flags",{"name":21,"slug":22,"type":15},"Tech Debt","tech-debt",59,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin","2026-04-06T18:44:31.93061",null,11,[29,30,31,32],"claude-code-plugin","codex-plugin","cursor-plugin","gemini-cli-extension",{"repoUrl":24,"stars":23,"forks":27,"topics":34,"description":35},[29,30,31,32],"Official PostHog plugin for Claude Code, Cursor, Gemini, Codex and other AI coding tools","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fai-plugin\u002Ftree\u002FHEAD\u002Fskills\u002Fcleaning-up-stale-feature-flags","---\nname: cleaning-up-stale-feature-flags\ndescription: 'Identify and clean up stale feature flags in a PostHog project. Use when the user wants to find unused, fully rolled out, or abandoned feature flags, review them for safety, and then disable or delete them. Covers staleness detection, dependency checking, and safe removal workflows.'\n---\n\n# Cleaning up stale feature flags\n\nThis skill guides you through finding feature flags that are no longer serving a purpose and safely removing them.\n\n## When to use this skill\n\n- The user asks to clean up, audit, or review their feature flags\n- The user wants to find flags that are stale, unused, or fully rolled out\n- The user asks \"which feature flags can I remove?\" or similar\n- The user wants to reduce tech debt from old feature flags\n\n## What makes a flag stale\n\nA feature flag is considered stale when it's no longer doing useful work. PostHog tracks this with two signals:\n\n1. **Usage-based staleness**: The flag has `last_called_at` data, but hasn't been evaluated in 30+ days. This is the strongest signal — the SDKs are no longer checking this flag.\n2. **Configuration-based staleness**: The flag has no usage data (`last_called_at` is null), is 30+ days old, and is 100% rolled out (boolean at 100% with no property filters, or a multivariate flag with one variant at 100%). A fully rolled out flag with no conditions is equivalent to a hardcoded value — it can be replaced by removing the flag check from code.\n\nDisabled flags (`active: false`) are not considered stale — they were intentionally turned off and may be kept for reactivation.\n\n## Workflow\n\n### 1. List stale flags\n\nCall `posthog:feature-flag-get-all` with `active: \"STALE\"`. This returns all stale flags in a single request — PostHog handles the staleness detection server-side using the criteria described above.\n\n### 2. Assess each candidate\n\nFor each stale flag, gather context before recommending action:\n\n**Check if it's tied to an experiment:**\n\nThe `posthog:feature-flag-get-definition` tool returns an `experiment_set` field. If non-empty, the flag is used by an experiment — check the experiment status before touching it.\n\n**Check if other flags depend on it:**\n\nFeature flags can have dependencies (flag B only evaluates when flag A is true). The flag definition includes dependency information in its `filters`. Look for `flag_key` references in other flags' filter groups.\n\n**Check when it was last modified:**\n\nA flag last updated years ago with no recent calls is a stronger removal candidate than one updated last month with no calls (it might be newly deployed and waiting for a release).\n\n**Summarize for the user:**\n\nFor each stale flag, present:\n\n- Flag key and description\n- Why it's considered stale (no calls in N days, or fully rolled out for N days)\n- Whether it's tied to experiments\n- When it was created and last modified\n- A recommended action (clean up from code and disable, or keep with explanation)\n\n### 3. Generate code cleanup instructions\n\nGenerate a cleanup prompt the user can run in their code editor or coding agent. The cleanup instructions must be tailored to each flag's rollout state, because the rollout state determines which code path to keep. This list also serves as the approval checklist — if the user says their code is already cleaned up, they review it and confirm which flags to disable.\n\nClassify each flag into one of three rollout states based on its definition:\n\n- **`fully_rolled_out`**: A boolean flag with a release condition at 100% rollout and no property filters, or a multivariate flag where one variant is at 100%. Record which variant was active (for multivariate flags).\n- **`not_rolled_out`**: All release conditions are at 0%, or the flag has no release conditions at all.\n- **`partial`**: Everything else — the flag had some targeting but wasn't fully rolled out or fully off.\n\nThen generate instructions following this structure:\n\n**For fully rolled out boolean flags** — remove the flag check but keep the enabled code path:\n\n```text\nSearch for: isFeatureEnabled, useFeatureFlag, getFeatureFlag, posthog.isFeatureEnabled, posthog.getFeatureFlag\n\nFor flag \"example-flag\":\n- Remove the if-check, keep the body\n- If there is an else branch, remove the else branch entirely\n```\n\n**For fully rolled out multivariate flags** — keep only the winning variant's code:\n\n```text\nFor flag \"example-flag\" (keep variant: \"winning-variant\"):\n- For if\u002Felse chains: keep only the branch matching \"winning-variant\", remove the flag check\n- For switch statements: keep only the winning variant's case, remove the switch\n```\n\n**For not-rolled-out flags** — remove the entire flag check AND the enabled code path:\n\n```text\nFor flag \"example-flag\":\n- Remove the if-check AND its body (the feature was never active)\n- If there is an else branch, keep only the else body\n```\n\n**For partial rollout flags** — flag these for manual review:\n\n```text\nFor flag \"example-flag\":\n- This flag had a partial rollout — check the flag's intent to determine which code path to keep\n- Then remove the flag check\n```\n\nEnd the instructions with: \"After cleanup, remove any dead code branches and unused imports.\"\n\nPresent the full cleanup prompt in a copyable format so the user can paste it directly into Claude Code, Cursor, Copilot, or any other AI code editor.\n\n### 4. Disable flags after code changes are deployed\n\n**Never disable flags before the code changes are deployed.** Disabling a fully rolled out flag while code still checks it will cause that code path to stop working — a production regression.\n\n**Never disable flags without explicit user approval.** Always present the list and recommendations first, then ask which flags to act on.\n\nPresent the user with both options and their tradeoffs:\n\n- **Disable** (`active: false`) via `posthog:update-feature-flag`: The flag stops being evaluated but the configuration is preserved. If something was missed in the code cleanup, re-enabling is instant. Recommended as the default.\n- **Delete** via `posthog:delete-feature-flag`: A soft-delete — the flag is marked as deleted but not physically removed. Keeps the flag list clean, but re-enabling requires recreating the flag. Better for flags the user is confident they'll never need again.\n\nOnce the user has chosen and confirms their code changes are deployed, apply the chosen action one flag at a time. Confirm each action so it's easy to stop if something goes wrong.\n\n## Example interaction\n\n```text\nUser: \"Can you help me clean up our stale feature flags?\"\n\nAgent steps:\n- Call posthog:feature-flag-get-all with active: \"STALE\" to get all stale flags in one request\n- For each stale flag, call posthog:feature-flag-get-definition to check experiment_set and dependencies\n- Present findings:\n\n   \"I found 7 stale feature flags in your project:\n\n   | Flag | Last called | Reason | Recommendation |\n   |------|-------------|--------|----------------|\n   | old-checkout-flow | 45 days ago | No evaluations in 45 days | Clean up and disable |\n   | beta-dashboard-v2 | Never | 100% rolled out, created 3 months ago | Clean up and disable |\n   | holiday-promo-2024 | 90 days ago | No evaluations in 90 days | Clean up and disable |\n   | new-pricing-page | 60 days ago | No evaluations in 60 days, tied to experiment #42 | Check experiment first |\n   ...\n\n   Want me to generate cleanup instructions for any of these? I'd recommend\n   starting with old-checkout-flow and beta-dashboard-v2 since they have no dependencies.\"\n\n- User confirms: \"Yes, do old-checkout-flow and beta-dashboard-v2\"\n- Classify rollout states from the flag definitions:\n   - old-checkout-flow: fully_rolled_out (boolean, 100% rollout, no conditions)\n   - beta-dashboard-v2: fully_rolled_out (boolean, 100% rollout, no conditions)\n- Generate and present cleanup prompt:\n\n   \"Here's a cleanup prompt you can paste into your code editor:\n\n   ---\n   Find and remove all references to these feature flags in the codebase.\n   For each flag, search for all usages: isFeatureEnabled, useFeatureFlag,\n   getFeatureFlag, posthog.isFeatureEnabled, posthog.getFeatureFlag, etc.\n\n   ## Flags that were rolled out to 100%\n   These flags were fully rolled out. Remove the flag check but KEEP the enabled code path.\n\n   Boolean flags (remove the if-check, keep the body):\n   - old-checkout-flow\n   - beta-dashboard-v2\n\n   If there is an else branch, remove the else branch entirely.\n   After cleanup, remove any dead code branches and unused imports.\n   ---\n\n   Once you've cleaned up your code and deployed, let me know.\n   Would you like to disable or delete these flags?\n   - Disable (recommended): keeps the config, re-enabling is instant\n   - Delete: removes from the list, but you'd need to recreate if needed\"\n\n- User confirms: \"Disable them, code is deployed\"\n- Disable each flag using posthog:update-feature-flag (active: false)\n- Confirm: \"Both flags are now disabled in PostHog.\"\n```\n\n## Important notes\n\n- **Code first, then disable.** Disabling a flag while code still references it causes the enabled code path to silently stop working. Always clean up code and deploy before disabling.\n- **Prefer disable over delete.** Disabling is instantly reversible. Deletion is not — re-enabling requires recreating the flag. Always present both options with tradeoffs and let the user choose.\n- **Always confirm before acting.** This skill involves disabling flags, which can affect production behavior. Never disable without explicit user approval.\n- **Disabled flags are not stale.** Don't recommend disabling flags that are already intentionally disabled — they may be kept for emergency reactivation.\n- **Experiment flags need extra care.** If a flag is tied to an active or recently completed experiment, the user likely wants to keep it until they've analyzed results.\n- **Seasonal flags may return.** Flags like \"black-friday-sale\" might look stale but are intentionally reused. Ask the user before removing these.\n- **Code cleanup is the real win.** Removing the flag from PostHog is the easy part. The value comes from removing the dead code paths.\n\n## Related tools\n\n- `posthog:feature-flag-get-all`: List and search feature flags (supports `active: \"STALE\"` filter)\n- `posthog:feature-flag-get-definition`: Get full flag details including experiment associations\n- `posthog:feature-flags-status-retrieve`: Get the status and reason for a single flag\n- `posthog:update-feature-flag`: Disable a flag by setting `active: false`\n- `posthog:delete-feature-flag`: Soft-delete a flag\n",{"data":39,"body":40},{"name":4,"description":6},{"type":41,"children":42},"root",[43,51,57,64,89,95,100,141,154,160,167,188,194,199,207,228,236,257,265,270,278,283,311,317,322,327,372,377,387,399,409,418,428,437,447,456,461,466,472,482,492,497,543,548,554,563,569,642,648],{"type":44,"tag":45,"props":46,"children":47},"element","h1",{"id":4},[48],{"type":49,"value":50},"text","Cleaning up stale feature flags",{"type":44,"tag":52,"props":53,"children":54},"p",{},[55],{"type":49,"value":56},"This skill guides you through finding feature flags that are no longer serving a purpose and safely removing them.",{"type":44,"tag":58,"props":59,"children":61},"h2",{"id":60},"when-to-use-this-skill",[62],{"type":49,"value":63},"When to use this skill",{"type":44,"tag":65,"props":66,"children":67},"ul",{},[68,74,79,84],{"type":44,"tag":69,"props":70,"children":71},"li",{},[72],{"type":49,"value":73},"The user asks to clean up, audit, or review their feature flags",{"type":44,"tag":69,"props":75,"children":76},{},[77],{"type":49,"value":78},"The user wants to find flags that are stale, unused, or fully rolled out",{"type":44,"tag":69,"props":80,"children":81},{},[82],{"type":49,"value":83},"The user asks \"which feature flags can I remove?\" or similar",{"type":44,"tag":69,"props":85,"children":86},{},[87],{"type":49,"value":88},"The user wants to reduce tech debt from old feature flags",{"type":44,"tag":58,"props":90,"children":92},{"id":91},"what-makes-a-flag-stale",[93],{"type":49,"value":94},"What makes a flag stale",{"type":44,"tag":52,"props":96,"children":97},{},[98],{"type":49,"value":99},"A feature flag is considered stale when it's no longer doing useful work. PostHog tracks this with two signals:",{"type":44,"tag":101,"props":102,"children":103},"ol",{},[104,124],{"type":44,"tag":69,"props":105,"children":106},{},[107,113,115,122],{"type":44,"tag":108,"props":109,"children":110},"strong",{},[111],{"type":49,"value":112},"Usage-based staleness",{"type":49,"value":114},": The flag has ",{"type":44,"tag":116,"props":117,"children":119},"code",{"className":118},[],[120],{"type":49,"value":121},"last_called_at",{"type":49,"value":123}," data, but hasn't been evaluated in 30+ days. This is the strongest signal — the SDKs are no longer checking this flag.",{"type":44,"tag":69,"props":125,"children":126},{},[127,132,134,139],{"type":44,"tag":108,"props":128,"children":129},{},[130],{"type":49,"value":131},"Configuration-based staleness",{"type":49,"value":133},": The flag has no usage data (",{"type":44,"tag":116,"props":135,"children":137},{"className":136},[],[138],{"type":49,"value":121},{"type":49,"value":140}," is null), is 30+ days old, and is 100% rolled out (boolean at 100% with no property filters, or a multivariate flag with one variant at 100%). A fully rolled out flag with no conditions is equivalent to a hardcoded value — it can be replaced by removing the flag check from code.",{"type":44,"tag":52,"props":142,"children":143},{},[144,146,152],{"type":49,"value":145},"Disabled flags (",{"type":44,"tag":116,"props":147,"children":149},{"className":148},[],[150],{"type":49,"value":151},"active: false",{"type":49,"value":153},") are not considered stale — they were intentionally turned off and may be kept for reactivation.",{"type":44,"tag":58,"props":155,"children":157},{"id":156},"workflow",[158],{"type":49,"value":159},"Workflow",{"type":44,"tag":161,"props":162,"children":164},"h3",{"id":163},"_1-list-stale-flags",[165],{"type":49,"value":166},"1. List stale flags",{"type":44,"tag":52,"props":168,"children":169},{},[170,172,178,180,186],{"type":49,"value":171},"Call ",{"type":44,"tag":116,"props":173,"children":175},{"className":174},[],[176],{"type":49,"value":177},"posthog:feature-flag-get-all",{"type":49,"value":179}," with ",{"type":44,"tag":116,"props":181,"children":183},{"className":182},[],[184],{"type":49,"value":185},"active: \"STALE\"",{"type":49,"value":187},". This returns all stale flags in a single request — PostHog handles the staleness detection server-side using the criteria described above.",{"type":44,"tag":161,"props":189,"children":191},{"id":190},"_2-assess-each-candidate",[192],{"type":49,"value":193},"2. Assess each candidate",{"type":44,"tag":52,"props":195,"children":196},{},[197],{"type":49,"value":198},"For each stale flag, gather context before recommending action:",{"type":44,"tag":52,"props":200,"children":201},{},[202],{"type":44,"tag":108,"props":203,"children":204},{},[205],{"type":49,"value":206},"Check if it's tied to an experiment:",{"type":44,"tag":52,"props":208,"children":209},{},[210,212,218,220,226],{"type":49,"value":211},"The ",{"type":44,"tag":116,"props":213,"children":215},{"className":214},[],[216],{"type":49,"value":217},"posthog:feature-flag-get-definition",{"type":49,"value":219}," tool returns an ",{"type":44,"tag":116,"props":221,"children":223},{"className":222},[],[224],{"type":49,"value":225},"experiment_set",{"type":49,"value":227}," field. If non-empty, the flag is used by an experiment — check the experiment status before touching it.",{"type":44,"tag":52,"props":229,"children":230},{},[231],{"type":44,"tag":108,"props":232,"children":233},{},[234],{"type":49,"value":235},"Check if other flags depend on it:",{"type":44,"tag":52,"props":237,"children":238},{},[239,241,247,249,255],{"type":49,"value":240},"Feature flags can have dependencies (flag B only evaluates when flag A is true). The flag definition includes dependency information in its ",{"type":44,"tag":116,"props":242,"children":244},{"className":243},[],[245],{"type":49,"value":246},"filters",{"type":49,"value":248},". Look for ",{"type":44,"tag":116,"props":250,"children":252},{"className":251},[],[253],{"type":49,"value":254},"flag_key",{"type":49,"value":256}," references in other flags' filter groups.",{"type":44,"tag":52,"props":258,"children":259},{},[260],{"type":44,"tag":108,"props":261,"children":262},{},[263],{"type":49,"value":264},"Check when it was last modified:",{"type":44,"tag":52,"props":266,"children":267},{},[268],{"type":49,"value":269},"A flag last updated years ago with no recent calls is a stronger removal candidate than one updated last month with no calls (it might be newly deployed and waiting for a release).",{"type":44,"tag":52,"props":271,"children":272},{},[273],{"type":44,"tag":108,"props":274,"children":275},{},[276],{"type":49,"value":277},"Summarize for the user:",{"type":44,"tag":52,"props":279,"children":280},{},[281],{"type":49,"value":282},"For each stale flag, present:",{"type":44,"tag":65,"props":284,"children":285},{},[286,291,296,301,306],{"type":44,"tag":69,"props":287,"children":288},{},[289],{"type":49,"value":290},"Flag key and description",{"type":44,"tag":69,"props":292,"children":293},{},[294],{"type":49,"value":295},"Why it's considered stale (no calls in N days, or fully rolled out for N days)",{"type":44,"tag":69,"props":297,"children":298},{},[299],{"type":49,"value":300},"Whether it's tied to experiments",{"type":44,"tag":69,"props":302,"children":303},{},[304],{"type":49,"value":305},"When it was created and last modified",{"type":44,"tag":69,"props":307,"children":308},{},[309],{"type":49,"value":310},"A recommended action (clean up from code and disable, or keep with explanation)",{"type":44,"tag":161,"props":312,"children":314},{"id":313},"_3-generate-code-cleanup-instructions",[315],{"type":49,"value":316},"3. Generate code cleanup instructions",{"type":44,"tag":52,"props":318,"children":319},{},[320],{"type":49,"value":321},"Generate a cleanup prompt the user can run in their code editor or coding agent. The cleanup instructions must be tailored to each flag's rollout state, because the rollout state determines which code path to keep. This list also serves as the approval checklist — if the user says their code is already cleaned up, they review it and confirm which flags to disable.",{"type":44,"tag":52,"props":323,"children":324},{},[325],{"type":49,"value":326},"Classify each flag into one of three rollout states based on its definition:",{"type":44,"tag":65,"props":328,"children":329},{},[330,344,358],{"type":44,"tag":69,"props":331,"children":332},{},[333,342],{"type":44,"tag":108,"props":334,"children":335},{},[336],{"type":44,"tag":116,"props":337,"children":339},{"className":338},[],[340],{"type":49,"value":341},"fully_rolled_out",{"type":49,"value":343},": A boolean flag with a release condition at 100% rollout and no property filters, or a multivariate flag where one variant is at 100%. Record which variant was active (for multivariate flags).",{"type":44,"tag":69,"props":345,"children":346},{},[347,356],{"type":44,"tag":108,"props":348,"children":349},{},[350],{"type":44,"tag":116,"props":351,"children":353},{"className":352},[],[354],{"type":49,"value":355},"not_rolled_out",{"type":49,"value":357},": All release conditions are at 0%, or the flag has no release conditions at all.",{"type":44,"tag":69,"props":359,"children":360},{},[361,370],{"type":44,"tag":108,"props":362,"children":363},{},[364],{"type":44,"tag":116,"props":365,"children":367},{"className":366},[],[368],{"type":49,"value":369},"partial",{"type":49,"value":371},": Everything else — the flag had some targeting but wasn't fully rolled out or fully off.",{"type":44,"tag":52,"props":373,"children":374},{},[375],{"type":49,"value":376},"Then generate instructions following this structure:",{"type":44,"tag":52,"props":378,"children":379},{},[380,385],{"type":44,"tag":108,"props":381,"children":382},{},[383],{"type":49,"value":384},"For fully rolled out boolean flags",{"type":49,"value":386}," — remove the flag check but keep the enabled code path:",{"type":44,"tag":388,"props":389,"children":394},"pre",{"className":390,"code":392,"language":49,"meta":393},[391],"language-text","Search for: isFeatureEnabled, useFeatureFlag, getFeatureFlag, posthog.isFeatureEnabled, posthog.getFeatureFlag\n\nFor flag \"example-flag\":\n- Remove the if-check, keep the body\n- If there is an else branch, remove the else branch entirely\n","",[395],{"type":44,"tag":116,"props":396,"children":397},{"__ignoreMap":393},[398],{"type":49,"value":392},{"type":44,"tag":52,"props":400,"children":401},{},[402,407],{"type":44,"tag":108,"props":403,"children":404},{},[405],{"type":49,"value":406},"For fully rolled out multivariate flags",{"type":49,"value":408}," — keep only the winning variant's code:",{"type":44,"tag":388,"props":410,"children":413},{"className":411,"code":412,"language":49,"meta":393},[391],"For flag \"example-flag\" (keep variant: \"winning-variant\"):\n- For if\u002Felse chains: keep only the branch matching \"winning-variant\", remove the flag check\n- For switch statements: keep only the winning variant's case, remove the switch\n",[414],{"type":44,"tag":116,"props":415,"children":416},{"__ignoreMap":393},[417],{"type":49,"value":412},{"type":44,"tag":52,"props":419,"children":420},{},[421,426],{"type":44,"tag":108,"props":422,"children":423},{},[424],{"type":49,"value":425},"For not-rolled-out flags",{"type":49,"value":427}," — remove the entire flag check AND the enabled code path:",{"type":44,"tag":388,"props":429,"children":432},{"className":430,"code":431,"language":49,"meta":393},[391],"For flag \"example-flag\":\n- Remove the if-check AND its body (the feature was never active)\n- If there is an else branch, keep only the else body\n",[433],{"type":44,"tag":116,"props":434,"children":435},{"__ignoreMap":393},[436],{"type":49,"value":431},{"type":44,"tag":52,"props":438,"children":439},{},[440,445],{"type":44,"tag":108,"props":441,"children":442},{},[443],{"type":49,"value":444},"For partial rollout flags",{"type":49,"value":446}," — flag these for manual review:",{"type":44,"tag":388,"props":448,"children":451},{"className":449,"code":450,"language":49,"meta":393},[391],"For flag \"example-flag\":\n- This flag had a partial rollout — check the flag's intent to determine which code path to keep\n- Then remove the flag check\n",[452],{"type":44,"tag":116,"props":453,"children":454},{"__ignoreMap":393},[455],{"type":49,"value":450},{"type":44,"tag":52,"props":457,"children":458},{},[459],{"type":49,"value":460},"End the instructions with: \"After cleanup, remove any dead code branches and unused imports.\"",{"type":44,"tag":52,"props":462,"children":463},{},[464],{"type":49,"value":465},"Present the full cleanup prompt in a copyable format so the user can paste it directly into Claude Code, Cursor, Copilot, or any other AI code editor.",{"type":44,"tag":161,"props":467,"children":469},{"id":468},"_4-disable-flags-after-code-changes-are-deployed",[470],{"type":49,"value":471},"4. Disable flags after code changes are deployed",{"type":44,"tag":52,"props":473,"children":474},{},[475,480],{"type":44,"tag":108,"props":476,"children":477},{},[478],{"type":49,"value":479},"Never disable flags before the code changes are deployed.",{"type":49,"value":481}," Disabling a fully rolled out flag while code still checks it will cause that code path to stop working — a production regression.",{"type":44,"tag":52,"props":483,"children":484},{},[485,490],{"type":44,"tag":108,"props":486,"children":487},{},[488],{"type":49,"value":489},"Never disable flags without explicit user approval.",{"type":49,"value":491}," Always present the list and recommendations first, then ask which flags to act on.",{"type":44,"tag":52,"props":493,"children":494},{},[495],{"type":49,"value":496},"Present the user with both options and their tradeoffs:",{"type":44,"tag":65,"props":498,"children":499},{},[500,525],{"type":44,"tag":69,"props":501,"children":502},{},[503,508,510,515,517,523],{"type":44,"tag":108,"props":504,"children":505},{},[506],{"type":49,"value":507},"Disable",{"type":49,"value":509}," (",{"type":44,"tag":116,"props":511,"children":513},{"className":512},[],[514],{"type":49,"value":151},{"type":49,"value":516},") via ",{"type":44,"tag":116,"props":518,"children":520},{"className":519},[],[521],{"type":49,"value":522},"posthog:update-feature-flag",{"type":49,"value":524},": The flag stops being evaluated but the configuration is preserved. If something was missed in the code cleanup, re-enabling is instant. Recommended as the default.",{"type":44,"tag":69,"props":526,"children":527},{},[528,533,535,541],{"type":44,"tag":108,"props":529,"children":530},{},[531],{"type":49,"value":532},"Delete",{"type":49,"value":534}," via ",{"type":44,"tag":116,"props":536,"children":538},{"className":537},[],[539],{"type":49,"value":540},"posthog:delete-feature-flag",{"type":49,"value":542},": A soft-delete — the flag is marked as deleted but not physically removed. Keeps the flag list clean, but re-enabling requires recreating the flag. Better for flags the user is confident they'll never need again.",{"type":44,"tag":52,"props":544,"children":545},{},[546],{"type":49,"value":547},"Once the user has chosen and confirms their code changes are deployed, apply the chosen action one flag at a time. Confirm each action so it's easy to stop if something goes wrong.",{"type":44,"tag":58,"props":549,"children":551},{"id":550},"example-interaction",[552],{"type":49,"value":553},"Example interaction",{"type":44,"tag":388,"props":555,"children":558},{"className":556,"code":557,"language":49,"meta":393},[391],"User: \"Can you help me clean up our stale feature flags?\"\n\nAgent steps:\n- Call posthog:feature-flag-get-all with active: \"STALE\" to get all stale flags in one request\n- For each stale flag, call posthog:feature-flag-get-definition to check experiment_set and dependencies\n- Present findings:\n\n   \"I found 7 stale feature flags in your project:\n\n   | Flag | Last called | Reason | Recommendation |\n   |------|-------------|--------|----------------|\n   | old-checkout-flow | 45 days ago | No evaluations in 45 days | Clean up and disable |\n   | beta-dashboard-v2 | Never | 100% rolled out, created 3 months ago | Clean up and disable |\n   | holiday-promo-2024 | 90 days ago | No evaluations in 90 days | Clean up and disable |\n   | new-pricing-page | 60 days ago | No evaluations in 60 days, tied to experiment #42 | Check experiment first |\n   ...\n\n   Want me to generate cleanup instructions for any of these? I'd recommend\n   starting with old-checkout-flow and beta-dashboard-v2 since they have no dependencies.\"\n\n- User confirms: \"Yes, do old-checkout-flow and beta-dashboard-v2\"\n- Classify rollout states from the flag definitions:\n   - old-checkout-flow: fully_rolled_out (boolean, 100% rollout, no conditions)\n   - beta-dashboard-v2: fully_rolled_out (boolean, 100% rollout, no conditions)\n- Generate and present cleanup prompt:\n\n   \"Here's a cleanup prompt you can paste into your code editor:\n\n   ---\n   Find and remove all references to these feature flags in the codebase.\n   For each flag, search for all usages: isFeatureEnabled, useFeatureFlag,\n   getFeatureFlag, posthog.isFeatureEnabled, posthog.getFeatureFlag, etc.\n\n   ## Flags that were rolled out to 100%\n   These flags were fully rolled out. Remove the flag check but KEEP the enabled code path.\n\n   Boolean flags (remove the if-check, keep the body):\n   - old-checkout-flow\n   - beta-dashboard-v2\n\n   If there is an else branch, remove the else branch entirely.\n   After cleanup, remove any dead code branches and unused imports.\n   ---\n\n   Once you've cleaned up your code and deployed, let me know.\n   Would you like to disable or delete these flags?\n   - Disable (recommended): keeps the config, re-enabling is instant\n   - Delete: removes from the list, but you'd need to recreate if needed\"\n\n- User confirms: \"Disable them, code is deployed\"\n- Disable each flag using posthog:update-feature-flag (active: false)\n- Confirm: \"Both flags are now disabled in PostHog.\"\n",[559],{"type":44,"tag":116,"props":560,"children":561},{"__ignoreMap":393},[562],{"type":49,"value":557},{"type":44,"tag":58,"props":564,"children":566},{"id":565},"important-notes",[567],{"type":49,"value":568},"Important notes",{"type":44,"tag":65,"props":570,"children":571},{},[572,582,592,602,612,622,632],{"type":44,"tag":69,"props":573,"children":574},{},[575,580],{"type":44,"tag":108,"props":576,"children":577},{},[578],{"type":49,"value":579},"Code first, then disable.",{"type":49,"value":581}," Disabling a flag while code still references it causes the enabled code path to silently stop working. Always clean up code and deploy before disabling.",{"type":44,"tag":69,"props":583,"children":584},{},[585,590],{"type":44,"tag":108,"props":586,"children":587},{},[588],{"type":49,"value":589},"Prefer disable over delete.",{"type":49,"value":591}," Disabling is instantly reversible. Deletion is not — re-enabling requires recreating the flag. Always present both options with tradeoffs and let the user choose.",{"type":44,"tag":69,"props":593,"children":594},{},[595,600],{"type":44,"tag":108,"props":596,"children":597},{},[598],{"type":49,"value":599},"Always confirm before acting.",{"type":49,"value":601}," This skill involves disabling flags, which can affect production behavior. Never disable without explicit user approval.",{"type":44,"tag":69,"props":603,"children":604},{},[605,610],{"type":44,"tag":108,"props":606,"children":607},{},[608],{"type":49,"value":609},"Disabled flags are not stale.",{"type":49,"value":611}," Don't recommend disabling flags that are already intentionally disabled — they may be kept for emergency reactivation.",{"type":44,"tag":69,"props":613,"children":614},{},[615,620],{"type":44,"tag":108,"props":616,"children":617},{},[618],{"type":49,"value":619},"Experiment flags need extra care.",{"type":49,"value":621}," If a flag is tied to an active or recently completed experiment, the user likely wants to keep it until they've analyzed results.",{"type":44,"tag":69,"props":623,"children":624},{},[625,630],{"type":44,"tag":108,"props":626,"children":627},{},[628],{"type":49,"value":629},"Seasonal flags may return.",{"type":49,"value":631}," Flags like \"black-friday-sale\" might look stale but are intentionally reused. Ask the user before removing these.",{"type":44,"tag":69,"props":633,"children":634},{},[635,640],{"type":44,"tag":108,"props":636,"children":637},{},[638],{"type":49,"value":639},"Code cleanup is the real win.",{"type":49,"value":641}," Removing the flag from PostHog is the easy part. The value comes from removing the dead code paths.",{"type":44,"tag":58,"props":643,"children":645},{"id":644},"related-tools",[646],{"type":49,"value":647},"Related tools",{"type":44,"tag":65,"props":649,"children":650},{},[651,668,678,689,704],{"type":44,"tag":69,"props":652,"children":653},{},[654,659,661,666],{"type":44,"tag":116,"props":655,"children":657},{"className":656},[],[658],{"type":49,"value":177},{"type":49,"value":660},": List and search feature flags (supports ",{"type":44,"tag":116,"props":662,"children":664},{"className":663},[],[665],{"type":49,"value":185},{"type":49,"value":667}," filter)",{"type":44,"tag":69,"props":669,"children":670},{},[671,676],{"type":44,"tag":116,"props":672,"children":674},{"className":673},[],[675],{"type":49,"value":217},{"type":49,"value":677},": Get full flag details including experiment associations",{"type":44,"tag":69,"props":679,"children":680},{},[681,687],{"type":44,"tag":116,"props":682,"children":684},{"className":683},[],[685],{"type":49,"value":686},"posthog:feature-flags-status-retrieve",{"type":49,"value":688},": Get the status and reason for a single flag",{"type":44,"tag":69,"props":690,"children":691},{},[692,697,699],{"type":44,"tag":116,"props":693,"children":695},{"className":694},[],[696],{"type":49,"value":522},{"type":49,"value":698},": Disable a flag by setting ",{"type":44,"tag":116,"props":700,"children":702},{"className":701},[],[703],{"type":49,"value":151},{"type":44,"tag":69,"props":705,"children":706},{},[707,712],{"type":44,"tag":116,"props":708,"children":710},{"className":709},[],[711],{"type":49,"value":540},{"type":49,"value":713},": Soft-delete a flag",{"items":715,"total":886},[716,735,747,760,773,788,802,819,833,848,858,876],{"slug":717,"name":717,"fn":718,"description":719,"org":720,"tags":721,"stars":732,"repoUrl":733,"updatedAt":734},"analyzing-expensive-users","analyze expensive users in AI observability","Analyze the most expensive users in AI observability and explain why they cost so much. Use when the user asks about top spenders, expensive users, per-user LLM cost, user-level cost drivers, or patterns behind high AI observability spend.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[722,725,728,731],{"name":723,"slug":724,"type":15},"Analytics","analytics",{"name":726,"slug":727,"type":15},"Cost Optimization","cost-optimization",{"name":729,"slug":730,"type":15},"Observability","observability",{"name":9,"slug":8,"type":15},35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-28T05:34:11.117757",{"slug":736,"name":736,"fn":737,"description":738,"org":739,"tags":740,"stars":732,"repoUrl":733,"updatedAt":746},"auditing-endpoints","audit PostHog project 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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[741,742,745],{"name":723,"slug":724,"type":15},{"name":743,"slug":744,"type":15},"Audit","audit",{"name":9,"slug":8,"type":15},"2026-06-08T08:08:33.693989",{"slug":748,"name":748,"fn":749,"description":750,"org":751,"tags":752,"stars":732,"repoUrl":733,"updatedAt":759},"auditing-warehouse-source-health","audit PostHog data warehouse source health","Audit the health of a PostHog project's data warehouse sources and syncs — find every broken or degraded source connection, sync schema, and webhook channel. Use when the user asks \"why are my imports failing?\", \"what's broken with my sources?\", \"why is my warehouse data stale?\", or wants a one-shot triage of source\u002Fsync health before deciding where to dig in. Produces a prioritized report grouped by severity, with recommended next steps. For materialized-view health use `auditing-warehouse-view-health`; for a single failing sync use `diagnosing-failed-warehouse-syncs`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[753,754,757,758],{"name":743,"slug":744,"type":15},{"name":755,"slug":756,"type":15},"Data Warehouse","data-warehouse",{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:22:57.67984",{"slug":761,"name":761,"fn":762,"description":763,"org":764,"tags":765,"stars":732,"repoUrl":733,"updatedAt":772},"auditing-warehouse-view-health","audit PostHog materialized view health","Audit the health of a PostHog project's materialized views (saved queries) — find every failed materialization and flag unused or stale materialized views that cost storage and compute. Use when the user asks \"which of my views are broken?\", \"why is this materialized view failing?\", \"are any of my views wasting compute?\", or wants a one-shot triage of view health. For source\u002Fsync health use `auditing-warehouse-source-health`.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[766,767,768,771],{"name":743,"slug":744,"type":15},{"name":755,"slug":756,"type":15},{"name":769,"slug":770,"type":15},"Performance","performance",{"name":9,"slug":8,"type":15},"2026-06-18T08:25:10.936787",{"slug":774,"name":774,"fn":775,"description":776,"org":777,"tags":778,"stars":732,"repoUrl":733,"updatedAt":787},"authoring-error-tracking-alerts","author PostHog error tracking alerts","Author error tracking alerts that fire when an issue is created, reopened, or starts spiking. Use when the user asks to set up error notifications, route exceptions to Slack\u002Fwebhook\u002FLinear, or evaluate which error events are worth alerting on. Covers trigger-event selection, integration choice, dedup against existing alerts, and shipping with the canonical message body shape.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[779,782,785,786],{"name":780,"slug":781,"type":15},"Alerting","alerting",{"name":783,"slug":784,"type":15},"Debugging","debugging",{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},"2026-06-18T08:24:40.318583",{"slug":789,"name":789,"fn":790,"description":791,"org":792,"tags":793,"stars":732,"repoUrl":733,"updatedAt":801},"authoring-log-alerts","author log alerts in PostHog","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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[794,795,798,799,800],{"name":723,"slug":724,"type":15},{"name":796,"slug":797,"type":15},"Monitoring","monitoring",{"name":729,"slug":730,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-07-18T05:10:54.430898",{"slug":803,"name":803,"fn":804,"description":805,"org":806,"tags":807,"stars":732,"repoUrl":733,"updatedAt":818},"building-workflows","build and edit PostHog workflows","Build, edit, test, enable, and monitor PostHog workflows over MCP. Author the action\u002Fedge graph so it runs and opens cleanly in the visual editor, then change drafts surgically with patch operations. Use when asked to build, set up, automate, change, fix, or debug a workflow, campaign, broadcast, drip sequence, or event-triggered automation in the workflows product.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[808,811,814,815],{"name":809,"slug":810,"type":15},"Automation","automation",{"name":812,"slug":813,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},{"name":816,"slug":817,"type":15},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",{"slug":820,"name":820,"fn":821,"description":822,"org":823,"tags":824,"stars":732,"repoUrl":733,"updatedAt":832},"check-posthog-loading","inspect PostHog SDK loading across URLs","Inspect how the PostHog JavaScript SDK is loaded across a list of URLs. Use to confirm consistent installation across pages, find pages missing the snippet, detect mismatched API keys or hosts between pages, and verify the load method (head snippet vs deferred vs array.js).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[825,826,827,830,831],{"name":723,"slug":724,"type":15},{"name":783,"slug":784,"type":15},{"name":828,"slug":829,"type":15},"Frontend","frontend",{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},"2026-05-07T05:56:19.828048",{"slug":834,"name":834,"fn":835,"description":836,"org":837,"tags":838,"stars":732,"repoUrl":733,"updatedAt":847},"consuming-endpoints-from-client-code","integrate PostHog endpoints into client applications","Wire a PostHog endpoint into a client app or SDK. Covers fetching the OpenAPI spec, generating a typed client with openapi-generator or @hey-api\u002Fopenapi-ts, sending the right auth header, shaping the variables payload (HogQL code_name vs insight breakdown property), handling rate-limit and materialised-endpoint error responses. Use when the user says \"how do I call my endpoint\", \"generate a client for this\", or \"what auth header do I use\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[839,842,843,844],{"name":840,"slug":841,"type":15},"API Development","api-development",{"name":828,"slug":829,"type":15},{"name":9,"slug":8,"type":15},{"name":845,"slug":846,"type":15},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":849,"name":849,"fn":850,"description":851,"org":852,"tags":853,"stars":732,"repoUrl":733,"updatedAt":857},"copying-endpoints-across-projects","copy PostHog endpoints across projects","Copy a PostHog endpoint (a saved HogQL\u002Finsight query exposed as an API route) to another project in the same organization, or duplicate it under a new name in the same project. Use when the user wants to duplicate an endpoint, promote an endpoint from staging to production, replicate an endpoint's query\u002Fvariables\u002Ffreshness config in another workspace, or clone an endpoint to iterate on it. Unlike feature flags and experiments, endpoints have NO native cross-project copy tool — this skill covers the read-then-recreate flow (endpoint-get then endpoint-create), the active-project switching it requires, name-collision checks, and the safe defaults (land unmaterialised in the target, verify with endpoint-run). Does not cover editing endpoint versions (see managing-endpoint-versions) or authoring a brand-new endpoint from scratch (see creating-an-endpoint).\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[854,855,856],{"name":840,"slug":841,"type":15},{"name":13,"slug":14,"type":15},{"name":9,"slug":8,"type":15},"2026-07-15T05:29:58.442727",{"slug":859,"name":859,"fn":860,"description":861,"org":862,"tags":863,"stars":732,"repoUrl":733,"updatedAt":875},"creating-ai-subscription","schedule recurring AI-generated PostHog reports","Create a recurring AI-generated PostHog report — schedule a free-text prompt to run on a cron, with the LLM-synthesized markdown delivered to email or Slack on each tick. Use when the user wants a recurring AI summary of X on any cadence (daily, weekly, monthly, yearly) rather than a one-off report. (To attach an AI summary to an existing insight\u002Fdashboard subscription instead of a free-text prompt, see `managing-subscriptions` and its `summary_enabled` option.)\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[864,865,868,869,872],{"name":809,"slug":810,"type":15},{"name":866,"slug":867,"type":15},"Email","email",{"name":9,"slug":8,"type":15},{"name":870,"slug":871,"type":15},"Reporting","reporting",{"name":873,"slug":874,"type":15},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":877,"name":877,"fn":878,"description":879,"org":880,"tags":881,"stars":732,"repoUrl":733,"updatedAt":885},"creating-an-endpoint","create PostHog API endpoints","Create a PostHog endpoint with the right shape on the first try — covers query kind choice, name conventions, what to expose as variables (HogQL code_name vs insight breakdown), data_freshness_seconds, and whether to materialise on day one. Use when the user says \"create an endpoint\", \"expose this query as an API\", \"turn this insight into an endpoint\", or asks for help structuring a new endpoint. Steers away from common mistakes: materialising a query with cohort breakdowns or compare mode, inline-only variables on a materialised endpoint, unbounded date ranges, ambiguous names.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[882,883,884],{"name":723,"slug":724,"type":15},{"name":840,"slug":841,"type":15},{"name":9,"slug":8,"type":15},"2026-06-08T08:08:29.624498",231,{"items":888,"total":992},[889,904,920,933,946,958,976],{"slug":890,"name":890,"fn":891,"description":892,"org":893,"tags":894,"stars":23,"repoUrl":24,"updatedAt":903},"analyzing-experiment-session-replays","analyze session replays for PostHog experiments","Analyze session replay patterns across experiment variants to understand user behavior differences. Use when the user wants to see how users interact with different experiment variants, identify usability issues, compare behavior patterns between control and test groups, or get qualitative insights to complement quantitative experiment results.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[895,896,899,900],{"name":723,"slug":724,"type":15},{"name":897,"slug":898,"type":15},"Design","design",{"name":9,"slug":8,"type":15},{"name":901,"slug":902,"type":15},"User Research","user-research","2026-04-06T18:44:38.291781",{"slug":905,"name":905,"fn":906,"description":907,"org":908,"tags":909,"stars":23,"repoUrl":24,"updatedAt":919},"assessing-heatmaps","analyze page heatmaps and suggest improvements","Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click \u002F rageclick \u002F scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements.\nTRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap\u002Fclick data, or to 'analyze\u002Fassess\u002Freview the heatmap' for a URL.\nDO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[910,911,912,913,916],{"name":723,"slug":724,"type":15},{"name":828,"slug":829,"type":15},{"name":9,"slug":8,"type":15},{"name":914,"slug":915,"type":15},"Product Management","product-management",{"name":917,"slug":918,"type":15},"UX Design","ux-design","2026-06-05T07:40:43.37798",{"slug":921,"name":921,"fn":922,"description":923,"org":924,"tags":925,"stars":23,"repoUrl":24,"updatedAt":932},"auditing-experiments-flags","audit PostHog experiments and feature flags","Audit PostHog experiments and feature flags for configuration issues, staleness, and best-practice violations. Read when the user asks to audit, health-check, or review experiments or feature flags, check flag hygiene, or verify experiment setup.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[926,927,928,929],{"name":743,"slug":744,"type":15},{"name":18,"slug":19,"type":15},{"name":9,"slug":8,"type":15},{"name":930,"slug":931,"type":15},"QA","qa","2026-04-06T18:44:30.657553",{"slug":934,"name":934,"fn":935,"description":936,"org":937,"tags":938,"stars":23,"repoUrl":24,"updatedAt":945},"authoring-scouts","author and edit PostHog Signals scouts","How to author, edit, and adapt PostHog Signals scouts — the scheduled agents that scan a project and write reports into the Signals inbox. Use when a user wants to customize a canonical scout for their own setup (narrow its scope, retune its thresholds, add disqualifiers), tweak a scout's schedule or dry-run posture, or write a brand-new scout from scratch for a specific use case (a custom event, a product surface no canonical scout covers), or steer a scout without editing it at all by leaving it a note. Covers the scout SKILL.md anatomy, the report contract, the dedupe + scratchpad-memory conventions, the scout-notes steering channel, the per-team skills-store path vs the canonical in-repo path, and the write-and-inspect test loop (with dry-run as an optional safety net). Trigger on \"write\u002Fedit\u002Fcustomize a signals scout\", \"new scout for X\", \"tune my scout schedule\", \"make a scout that watches \u003Cevent>\", \"leave a note for \u002F give feedback to a scout\", \"tell the scouts about X\".\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[939,942,943,944],{"name":940,"slug":941,"type":15},"Agents","agents",{"name":809,"slug":810,"type":15},{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},"2026-07-28T05:33:45.509154",{"slug":947,"name":947,"fn":948,"description":949,"org":950,"tags":951,"stars":23,"repoUrl":24,"updatedAt":957},"building-a-dashboard","build and update PostHog dashboards","Build a new dashboard, or update an existing one, from a set of insights — the same job the in-app assistant does with its upsert-dashboard tool, but over MCP. Use when a user asks to create a dashboard, put several metrics\u002Fcharts together on one page, assemble a dashboard for a topic (product analytics, retention, revenue, activation, etc.), or add\u002Fremove\u002Freplace insights on a dashboard they already have. Covers deciding create vs update, reusing existing insights vs creating new ones, and using PostHog's vetted dashboard templates as reference for what a strong dashboard on a topic looks like.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[952,953,956],{"name":723,"slug":724,"type":15},{"name":954,"slug":955,"type":15},"Dashboards","dashboards",{"name":812,"slug":813,"type":15},"2026-07-21T06:07:38.060598",{"slug":959,"name":959,"fn":960,"description":961,"org":962,"tags":963,"stars":23,"repoUrl":24,"updatedAt":975},"checking-deploy-timing","correlate PostHog deployments with GitHub commits","Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask \"when was X deployed\", \"is my change live in the US\u002FEU yet\", \"has my PR shipped\", \"did the fix roll out to prod-us\", or otherwise want to know whether\u002Fwhen a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event\u002Fdata volume alone — that only shows when data changed, not when code shipped.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[964,967,970,973,974],{"name":965,"slug":966,"type":15},"Deployment","deployment",{"name":968,"slug":969,"type":15},"Git","git",{"name":971,"slug":972,"type":15},"GitHub","github",{"name":729,"slug":730,"type":15},{"name":9,"slug":8,"type":15},"2026-06-28T07:46:59.53536",{"slug":977,"name":977,"fn":978,"description":979,"org":980,"tags":981,"stars":23,"repoUrl":24,"updatedAt":991},"choosing-trend-or-slope-view","visualize trends and growth over time","Clarify how to visualize change over a time range before building a trend. Use whenever the user asks how much something changed, grew, dropped, improved, or regressed between two points or periods — \"how much did X change from A to B\", \"before vs after\", \"start vs end\", \"week over week\", \"compare this month to last\", \"change over time\" — or mentions a \"slope chart\" \u002F \"slopegraph\". Two readings of \"change\" need different charts: the whole trend (a line, every interval) versus just the two endpoints (a slope, start vs end). Ask which they want, then render it. Not for choosing a saved insight ChartDisplayType in the insight editor.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[982,983,986,989,990],{"name":723,"slug":724,"type":15},{"name":984,"slug":985,"type":15},"Charts","charts",{"name":987,"slug":988,"type":15},"Data Visualization","data-visualization",{"name":9,"slug":8,"type":15},{"name":870,"slug":871,"type":15},"2026-06-18T08:18:57.960157",56]