[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-posthog-review-hog-perspective-logic-correctness":3,"mdc-mr2ra0-key":49,"related-repo-posthog-review-hog-perspective-logic-correctness":460,"related-org-posthog-review-hog-perspective-logic-correctness":564},{"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":44,"sourceUrl":47,"mdContent":48},"review-hog-perspective-logic-correctness","review code logic and correctness","The Logic & Correctness review perspective for ReviewHog. Verifies that changed code does what it is supposed to do — business logic, edge cases, data transformations, and query \u002F data-access correctness. Reports correctness issues only; security and performance are separate perspectives.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"posthog","PostHog","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fposthog.png",[12,14,17,20],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"Code Review","code-review",{"name":18,"slug":19,"type":13},"Engineering","engineering",{"name":21,"slug":22,"type":13},"Code Analysis","code-analysis",35568,"https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog","2026-07-15T05:30:21.952102",null,2977,[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"ab-testing","ai-analytics","analytics","cdp","data-warehouse","experiments","feature-flags","javascript","product-analytics","python","react","session-replay","surveys","typescript","web-analytics",{"repoUrl":24,"stars":23,"forks":27,"topics":45,"description":46},[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"🦔 PostHog is an all-in-one developer platform for building successful products. We offer product analytics, web analytics, session replay, error tracking, feature flags, experimentation, surveys, data warehouse, a CDP, and an AI product assistant to help debug your code, ship features faster, and keep all your usage and customer data in one stack.","https:\u002F\u002Fgithub.com\u002FPostHog\u002Fposthog\u002Ftree\u002FHEAD\u002Fproducts\u002Freview_hog\u002Fskills\u002Freview-hog-perspective-logic-correctness","---\nname: review-hog-perspective-logic-correctness\ndescription: >\n  The Logic & Correctness review perspective for ReviewHog. Verifies that changed code does what it\n  is supposed to do — business logic, edge cases, data transformations, and query \u002F data-access\n  correctness. Reports correctness issues only; security and performance are separate perspectives.\nmetadata:\n  owner_team: review_hog\n  perspective: logic_correctness\n---\n\n# Review perspective: Logic & Correctness\n\nYou are reviewing a PR chunk through the **Logic & Correctness** perspective: does the code do what\nit is supposed to do? Concentrate on business-logic correctness, edge cases, data transformations,\nand query \u002F data-access logic.\n\nThis is one of several independent perspectives reviewing the same chunk in parallel — security and\nperformance are covered elsewhere. Stay in your lane, and report every correctness issue you find\nwithout worrying about what another perspective might also report (overlap is resolved later by a\nseparate deduplication step).\n\n## Primary investigation areas\n\n1. **Business logic implementation**\n   - Verify calculations and algorithms are correct\n   - Check for off-by-one errors and boundary conditions\n   - Validate conditional logic and branching\n   - Ensure edge cases are handled properly\n   - Verify assumptions about data are valid\n\n2. **Data transformations & mutations**\n   - Check data mapping between layers is accurate\n   - Verify state mutations (especially in frontend code)\n   - Ensure no data loss during transformations\n   - Validate type coercions and conversions\n\n3. **Query & data-access logic**\n   - Verify SQL \u002F database queries are correct\n   - Validate that sync SQL queries aren't issued from an async context (blocking the thread)\n   - Check JOIN conditions and WHERE clauses\n   - Validate aggregation logic\n   - Ensure deterministic ordering where needed\n   - Check transaction boundaries\n\n4. **LLM prompt engineering** (if applicable)\n   - Verify prompts have clear, unambiguous instructions\n   - Check for missing examples in prompts\n   - Validate output parsing logic\n   - Ensure token-limit handling\n\n## Investigation commands\n\n- Find calculation logic: `rg \"calculate|compute|aggregate\" --type py -A 5`\n- Check conditionals: `rg \"if.*else|switch|case\" --type py -B 2 -A 5`\n- Find data transformations: `rg \"map|transform|convert|parse\" --type py -A 3`\n- Locate queries: `rg \"SELECT|JOIN|WHERE|GROUP BY\" --type sql -A 10`\n- Find state mutations: `rg \"setState|mutation|update.*state\" --type js --type tsx -A 3`\n\n## Where to focus\n\nConcentrate on files that carry real logic:\n\n- Business-logic implementation files\n- Data transformation and processing code\n- Database query files and data-access layers\n- API handlers and service implementations\n- Frontend components with logic (not just UI)\n\nRead documentation and pure configuration files for context, but don't raise logic findings on\nthem — and detect issues only in non-test files (test files have their own patterns; reference them\nfor context when validating a finding in production code).\n\n## What to leave to other perspectives\n\n- Performance optimizations and error-handling completeness → Performance & Reliability\n- Security vulnerabilities and API-contract changes → Contracts & Security\n- Code style or formatting → not a ReviewHog concern\n\n## Key questions\n\n- Does the implementation match the intended behavior?\n- Are all edge cases and error conditions handled?\n- Is the logic flow clear and correct?\n- Are calculations and transformations accurate?\n- Do queries return the expected results?\n- Is data integrity maintained throughout operations?\n\n## What a valid finding looks like\n\nA Logic & Correctness finding relates to:\n\n- Incorrect logic or algorithms\n- Missing edge-case handling\n- Wrong calculations or formulas\n- Incorrect data transformations\n- Query-logic errors\n- State-management bugs\n- Incorrect assumptions about data\n",{"data":50,"body":54},{"name":4,"description":6,"metadata":51},{"owner_team":52,"perspective":53},"review_hog","logic_correctness",{"type":55,"children":56},"root",[57,66,80,85,92,239,245,304,310,315,343,348,354,372,378,411,417,422],{"type":58,"tag":59,"props":60,"children":62},"element","h1",{"id":61},"review-perspective-logic-correctness",[63],{"type":64,"value":65},"text","Review perspective: Logic & Correctness",{"type":58,"tag":67,"props":68,"children":69},"p",{},[70,72,78],{"type":64,"value":71},"You are reviewing a PR chunk through the ",{"type":58,"tag":73,"props":74,"children":75},"strong",{},[76],{"type":64,"value":77},"Logic & Correctness",{"type":64,"value":79}," perspective: does the code do what\nit is supposed to do? Concentrate on business-logic correctness, edge cases, data transformations,\nand query \u002F data-access logic.",{"type":58,"tag":67,"props":81,"children":82},{},[83],{"type":64,"value":84},"This is one of several independent perspectives reviewing the same chunk in parallel — security and\nperformance are covered elsewhere. Stay in your lane, and report every correctness issue you find\nwithout worrying about what another perspective might also report (overlap is resolved later by a\nseparate deduplication step).",{"type":58,"tag":86,"props":87,"children":89},"h2",{"id":88},"primary-investigation-areas",[90],{"type":64,"value":91},"Primary investigation areas",{"type":58,"tag":93,"props":94,"children":95},"ol",{},[96,134,165,206],{"type":58,"tag":97,"props":98,"children":99},"li",{},[100,105],{"type":58,"tag":73,"props":101,"children":102},{},[103],{"type":64,"value":104},"Business logic implementation",{"type":58,"tag":106,"props":107,"children":108},"ul",{},[109,114,119,124,129],{"type":58,"tag":97,"props":110,"children":111},{},[112],{"type":64,"value":113},"Verify calculations and algorithms are correct",{"type":58,"tag":97,"props":115,"children":116},{},[117],{"type":64,"value":118},"Check for off-by-one errors and boundary conditions",{"type":58,"tag":97,"props":120,"children":121},{},[122],{"type":64,"value":123},"Validate conditional logic and branching",{"type":58,"tag":97,"props":125,"children":126},{},[127],{"type":64,"value":128},"Ensure edge cases are handled properly",{"type":58,"tag":97,"props":130,"children":131},{},[132],{"type":64,"value":133},"Verify assumptions about data are valid",{"type":58,"tag":97,"props":135,"children":136},{},[137,142],{"type":58,"tag":73,"props":138,"children":139},{},[140],{"type":64,"value":141},"Data transformations & mutations",{"type":58,"tag":106,"props":143,"children":144},{},[145,150,155,160],{"type":58,"tag":97,"props":146,"children":147},{},[148],{"type":64,"value":149},"Check data mapping between layers is accurate",{"type":58,"tag":97,"props":151,"children":152},{},[153],{"type":64,"value":154},"Verify state mutations (especially in frontend code)",{"type":58,"tag":97,"props":156,"children":157},{},[158],{"type":64,"value":159},"Ensure no data loss during transformations",{"type":58,"tag":97,"props":161,"children":162},{},[163],{"type":64,"value":164},"Validate type coercions and conversions",{"type":58,"tag":97,"props":166,"children":167},{},[168,173],{"type":58,"tag":73,"props":169,"children":170},{},[171],{"type":64,"value":172},"Query & data-access logic",{"type":58,"tag":106,"props":174,"children":175},{},[176,181,186,191,196,201],{"type":58,"tag":97,"props":177,"children":178},{},[179],{"type":64,"value":180},"Verify SQL \u002F database queries are correct",{"type":58,"tag":97,"props":182,"children":183},{},[184],{"type":64,"value":185},"Validate that sync SQL queries aren't issued from an async context (blocking the thread)",{"type":58,"tag":97,"props":187,"children":188},{},[189],{"type":64,"value":190},"Check JOIN conditions and WHERE clauses",{"type":58,"tag":97,"props":192,"children":193},{},[194],{"type":64,"value":195},"Validate aggregation logic",{"type":58,"tag":97,"props":197,"children":198},{},[199],{"type":64,"value":200},"Ensure deterministic ordering where needed",{"type":58,"tag":97,"props":202,"children":203},{},[204],{"type":64,"value":205},"Check transaction boundaries",{"type":58,"tag":97,"props":207,"children":208},{},[209,214,216],{"type":58,"tag":73,"props":210,"children":211},{},[212],{"type":64,"value":213},"LLM prompt engineering",{"type":64,"value":215}," (if applicable)",{"type":58,"tag":106,"props":217,"children":218},{},[219,224,229,234],{"type":58,"tag":97,"props":220,"children":221},{},[222],{"type":64,"value":223},"Verify prompts have clear, unambiguous instructions",{"type":58,"tag":97,"props":225,"children":226},{},[227],{"type":64,"value":228},"Check for missing examples in prompts",{"type":58,"tag":97,"props":230,"children":231},{},[232],{"type":64,"value":233},"Validate output parsing logic",{"type":58,"tag":97,"props":235,"children":236},{},[237],{"type":64,"value":238},"Ensure token-limit handling",{"type":58,"tag":86,"props":240,"children":242},{"id":241},"investigation-commands",[243],{"type":64,"value":244},"Investigation commands",{"type":58,"tag":106,"props":246,"children":247},{},[248,260,271,282,293],{"type":58,"tag":97,"props":249,"children":250},{},[251,253],{"type":64,"value":252},"Find calculation logic: ",{"type":58,"tag":254,"props":255,"children":257},"code",{"className":256},[],[258],{"type":64,"value":259},"rg \"calculate|compute|aggregate\" --type py -A 5",{"type":58,"tag":97,"props":261,"children":262},{},[263,265],{"type":64,"value":264},"Check conditionals: ",{"type":58,"tag":254,"props":266,"children":268},{"className":267},[],[269],{"type":64,"value":270},"rg \"if.*else|switch|case\" --type py -B 2 -A 5",{"type":58,"tag":97,"props":272,"children":273},{},[274,276],{"type":64,"value":275},"Find data transformations: ",{"type":58,"tag":254,"props":277,"children":279},{"className":278},[],[280],{"type":64,"value":281},"rg \"map|transform|convert|parse\" --type py -A 3",{"type":58,"tag":97,"props":283,"children":284},{},[285,287],{"type":64,"value":286},"Locate queries: ",{"type":58,"tag":254,"props":288,"children":290},{"className":289},[],[291],{"type":64,"value":292},"rg \"SELECT|JOIN|WHERE|GROUP BY\" --type sql -A 10",{"type":58,"tag":97,"props":294,"children":295},{},[296,298],{"type":64,"value":297},"Find state mutations: ",{"type":58,"tag":254,"props":299,"children":301},{"className":300},[],[302],{"type":64,"value":303},"rg \"setState|mutation|update.*state\" --type js --type tsx -A 3",{"type":58,"tag":86,"props":305,"children":307},{"id":306},"where-to-focus",[308],{"type":64,"value":309},"Where to focus",{"type":58,"tag":67,"props":311,"children":312},{},[313],{"type":64,"value":314},"Concentrate on files that carry real logic:",{"type":58,"tag":106,"props":316,"children":317},{},[318,323,328,333,338],{"type":58,"tag":97,"props":319,"children":320},{},[321],{"type":64,"value":322},"Business-logic implementation files",{"type":58,"tag":97,"props":324,"children":325},{},[326],{"type":64,"value":327},"Data transformation and processing code",{"type":58,"tag":97,"props":329,"children":330},{},[331],{"type":64,"value":332},"Database query files and data-access layers",{"type":58,"tag":97,"props":334,"children":335},{},[336],{"type":64,"value":337},"API handlers and service implementations",{"type":58,"tag":97,"props":339,"children":340},{},[341],{"type":64,"value":342},"Frontend components with logic (not just UI)",{"type":58,"tag":67,"props":344,"children":345},{},[346],{"type":64,"value":347},"Read documentation and pure configuration files for context, but don't raise logic findings on\nthem — and detect issues only in non-test files (test files have their own patterns; reference them\nfor context when validating a finding in production code).",{"type":58,"tag":86,"props":349,"children":351},{"id":350},"what-to-leave-to-other-perspectives",[352],{"type":64,"value":353},"What to leave to other perspectives",{"type":58,"tag":106,"props":355,"children":356},{},[357,362,367],{"type":58,"tag":97,"props":358,"children":359},{},[360],{"type":64,"value":361},"Performance optimizations and error-handling completeness → Performance & Reliability",{"type":58,"tag":97,"props":363,"children":364},{},[365],{"type":64,"value":366},"Security vulnerabilities and API-contract changes → Contracts & Security",{"type":58,"tag":97,"props":368,"children":369},{},[370],{"type":64,"value":371},"Code style or formatting → not a ReviewHog concern",{"type":58,"tag":86,"props":373,"children":375},{"id":374},"key-questions",[376],{"type":64,"value":377},"Key questions",{"type":58,"tag":106,"props":379,"children":380},{},[381,386,391,396,401,406],{"type":58,"tag":97,"props":382,"children":383},{},[384],{"type":64,"value":385},"Does the implementation match the intended behavior?",{"type":58,"tag":97,"props":387,"children":388},{},[389],{"type":64,"value":390},"Are all edge cases and error conditions handled?",{"type":58,"tag":97,"props":392,"children":393},{},[394],{"type":64,"value":395},"Is the logic flow clear and correct?",{"type":58,"tag":97,"props":397,"children":398},{},[399],{"type":64,"value":400},"Are calculations and transformations accurate?",{"type":58,"tag":97,"props":402,"children":403},{},[404],{"type":64,"value":405},"Do queries return the expected results?",{"type":58,"tag":97,"props":407,"children":408},{},[409],{"type":64,"value":410},"Is data integrity maintained throughout operations?",{"type":58,"tag":86,"props":412,"children":414},{"id":413},"what-a-valid-finding-looks-like",[415],{"type":64,"value":416},"What a valid finding looks like",{"type":58,"tag":67,"props":418,"children":419},{},[420],{"type":64,"value":421},"A Logic & Correctness finding relates to:",{"type":58,"tag":106,"props":423,"children":424},{},[425,430,435,440,445,450,455],{"type":58,"tag":97,"props":426,"children":427},{},[428],{"type":64,"value":429},"Incorrect logic or algorithms",{"type":58,"tag":97,"props":431,"children":432},{},[433],{"type":64,"value":434},"Missing edge-case handling",{"type":58,"tag":97,"props":436,"children":437},{},[438],{"type":64,"value":439},"Wrong calculations or formulas",{"type":58,"tag":97,"props":441,"children":442},{},[443],{"type":64,"value":444},"Incorrect data transformations",{"type":58,"tag":97,"props":446,"children":447},{},[448],{"type":64,"value":449},"Query-logic errors",{"type":58,"tag":97,"props":451,"children":452},{},[453],{"type":64,"value":454},"State-management bugs",{"type":58,"tag":97,"props":456,"children":457},{},[458],{"type":64,"value":459},"Incorrect assumptions about data",{"items":461,"total":563},[462,478,490,502,515,530,546],{"slug":463,"name":463,"fn":464,"description":465,"org":466,"tags":467,"stars":23,"repoUrl":24,"updatedAt":477},"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},[468,470,473,476],{"name":469,"slug":31,"type":13},"Analytics",{"name":471,"slug":472,"type":13},"Cost Optimization","cost-optimization",{"name":474,"slug":475,"type":13},"Observability","observability",{"name":9,"slug":8,"type":13},"2026-07-28T05:34:11.117757",{"slug":479,"name":479,"fn":480,"description":481,"org":482,"tags":483,"stars":23,"repoUrl":24,"updatedAt":489},"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},[484,485,488],{"name":469,"slug":31,"type":13},{"name":486,"slug":487,"type":13},"Audit","audit",{"name":9,"slug":8,"type":13},"2026-06-08T08:08:33.693989",{"slug":491,"name":491,"fn":492,"description":493,"org":494,"tags":495,"stars":23,"repoUrl":24,"updatedAt":501},"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},[496,497,499,500],{"name":486,"slug":487,"type":13},{"name":498,"slug":33,"type":13},"Data Warehouse",{"name":474,"slug":475,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:22:57.67984",{"slug":503,"name":503,"fn":504,"description":505,"org":506,"tags":507,"stars":23,"repoUrl":24,"updatedAt":514},"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},[508,509,510,513],{"name":486,"slug":487,"type":13},{"name":498,"slug":33,"type":13},{"name":511,"slug":512,"type":13},"Performance","performance",{"name":9,"slug":8,"type":13},"2026-06-18T08:25:10.936787",{"slug":516,"name":516,"fn":517,"description":518,"org":519,"tags":520,"stars":23,"repoUrl":24,"updatedAt":529},"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},[521,524,527,528],{"name":522,"slug":523,"type":13},"Alerting","alerting",{"name":525,"slug":526,"type":13},"Debugging","debugging",{"name":474,"slug":475,"type":13},{"name":9,"slug":8,"type":13},"2026-06-18T08:24:40.318583",{"slug":531,"name":531,"fn":532,"description":533,"org":534,"tags":535,"stars":23,"repoUrl":24,"updatedAt":545},"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},[536,537,540,541,544],{"name":469,"slug":31,"type":13},{"name":538,"slug":539,"type":13},"Monitoring","monitoring",{"name":474,"slug":475,"type":13},{"name":542,"slug":543,"type":13},"Operations","operations",{"name":9,"slug":8,"type":13},"2026-07-18T05:10:54.430898",{"slug":547,"name":547,"fn":548,"description":549,"org":550,"tags":551,"stars":23,"repoUrl":24,"updatedAt":562},"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},[552,555,558,559],{"name":553,"slug":554,"type":13},"Automation","automation",{"name":556,"slug":557,"type":13},"MCP","mcp",{"name":9,"slug":8,"type":13},{"name":560,"slug":561,"type":13},"Workflow Automation","workflow-automation","2026-07-28T05:34:12.167015",61,{"items":565,"total":682},[566,573,579,586,593,600,608,615,629,644,654,672],{"slug":463,"name":463,"fn":464,"description":465,"org":567,"tags":568,"stars":23,"repoUrl":24,"updatedAt":477},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[569,570,571,572],{"name":469,"slug":31,"type":13},{"name":471,"slug":472,"type":13},{"name":474,"slug":475,"type":13},{"name":9,"slug":8,"type":13},{"slug":479,"name":479,"fn":480,"description":481,"org":574,"tags":575,"stars":23,"repoUrl":24,"updatedAt":489},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[576,577,578],{"name":469,"slug":31,"type":13},{"name":486,"slug":487,"type":13},{"name":9,"slug":8,"type":13},{"slug":491,"name":491,"fn":492,"description":493,"org":580,"tags":581,"stars":23,"repoUrl":24,"updatedAt":501},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[582,583,584,585],{"name":486,"slug":487,"type":13},{"name":498,"slug":33,"type":13},{"name":474,"slug":475,"type":13},{"name":9,"slug":8,"type":13},{"slug":503,"name":503,"fn":504,"description":505,"org":587,"tags":588,"stars":23,"repoUrl":24,"updatedAt":514},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[589,590,591,592],{"name":486,"slug":487,"type":13},{"name":498,"slug":33,"type":13},{"name":511,"slug":512,"type":13},{"name":9,"slug":8,"type":13},{"slug":516,"name":516,"fn":517,"description":518,"org":594,"tags":595,"stars":23,"repoUrl":24,"updatedAt":529},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[596,597,598,599],{"name":522,"slug":523,"type":13},{"name":525,"slug":526,"type":13},{"name":474,"slug":475,"type":13},{"name":9,"slug":8,"type":13},{"slug":531,"name":531,"fn":532,"description":533,"org":601,"tags":602,"stars":23,"repoUrl":24,"updatedAt":545},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[603,604,605,606,607],{"name":469,"slug":31,"type":13},{"name":538,"slug":539,"type":13},{"name":474,"slug":475,"type":13},{"name":542,"slug":543,"type":13},{"name":9,"slug":8,"type":13},{"slug":547,"name":547,"fn":548,"description":549,"org":609,"tags":610,"stars":23,"repoUrl":24,"updatedAt":562},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[611,612,613,614],{"name":553,"slug":554,"type":13},{"name":556,"slug":557,"type":13},{"name":9,"slug":8,"type":13},{"name":560,"slug":561,"type":13},{"slug":616,"name":616,"fn":617,"description":618,"org":619,"tags":620,"stars":23,"repoUrl":24,"updatedAt":628},"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},[621,622,623,626,627],{"name":469,"slug":31,"type":13},{"name":525,"slug":526,"type":13},{"name":624,"slug":625,"type":13},"Frontend","frontend",{"name":474,"slug":475,"type":13},{"name":9,"slug":8,"type":13},"2026-05-07T05:56:19.828048",{"slug":630,"name":630,"fn":631,"description":632,"org":633,"tags":634,"stars":23,"repoUrl":24,"updatedAt":643},"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},[635,638,639,640],{"name":636,"slug":637,"type":13},"API Development","api-development",{"name":624,"slug":625,"type":13},{"name":9,"slug":8,"type":13},{"name":641,"slug":642,"type":13},"SDK","sdk","2026-06-08T08:08:34.929454",{"slug":645,"name":645,"fn":646,"description":647,"org":648,"tags":649,"stars":23,"repoUrl":24,"updatedAt":653},"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},[650,651,652],{"name":636,"slug":637,"type":13},{"name":542,"slug":543,"type":13},{"name":9,"slug":8,"type":13},"2026-07-15T05:29:58.442727",{"slug":655,"name":655,"fn":656,"description":657,"org":658,"tags":659,"stars":23,"repoUrl":24,"updatedAt":671},"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},[660,661,664,665,668],{"name":553,"slug":554,"type":13},{"name":662,"slug":663,"type":13},"Email","email",{"name":9,"slug":8,"type":13},{"name":666,"slug":667,"type":13},"Reporting","reporting",{"name":669,"slug":670,"type":13},"Slack","slack","2026-06-09T07:32:27.935712",{"slug":673,"name":673,"fn":674,"description":675,"org":676,"tags":677,"stars":23,"repoUrl":24,"updatedAt":681},"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},[678,679,680],{"name":469,"slug":31,"type":13},{"name":636,"slug":637,"type":13},{"name":9,"slug":8,"type":13},"2026-06-08T08:08:29.624498",231]