survey-sdk-audit

Audit PostHog survey SDK feature parity across supported platforms.

37.6k|3.2k|Updated Jan 23, 2020
One-click install
npx skills add https://github.com/PostHog/posthog --skill survey-sdk-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: survey-sdk-audit
Source: https://github.com/PostHog/posthog/tree/main/.claude/skills/survey-sdk-audit
Command: npx skills add https://github.com/PostHog/posthog --skill survey-sdk-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit PostHog survey SDK features and version requirements across all supported platforms to identify parity gaps and reduce integration risk.

Core Features & Use Cases

  • Structured auditing of survey SDK support across posthog-js, posthog-ios, posthog-android, and posthog-flutter.
  • Comprehensive cross-SDK parity checks including changelog and code history.
  • Use Case: Before a release, run this audit to confirm surveyVersionRequirements.ts is consistently implemented across all SDKs and document any gaps as GitHub issues.

Quick Start

Start by configuring your SDK paths and running the audit to generate a parity report and issue list.

Frequently Asked Questions about survey-sdk-audit

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

FAQPage Schema
How do I audit PostHog survey SDK features across multiple platforms?

To audit PostHog survey SDK features, configure your SDK paths and run the audit to generate a parity report and issue list. It inspects changelogs, code history, and cross-SDK consistency to identify parity gaps across posthog-js, posthog-ios, posthog-android, and posthog-flutter.

What is SDK parity checking for survey version requirements?

SDK parity checking for survey version requirements is a structured validation process that confirms features like surveyVersionRequirements.ts are consistently implemented across all PostHog SDKs. It uses the browser reference implementation to drive checks and outputs structured metadata for GitHub issue creation.

Does PostHog survey SDK auditing support Flutter and iOS repositories?

Yes, PostHog survey SDK auditing supports Flutter and iOS repositories. It performs comprehensive cross-SDK parity checks across posthog-js, posthog-ios, posthog-android, and posthog-flutter, including inspecting changelogs and code history to document any integration gaps.

When do I need to run a cross-SDK parity audit for survey integrations?

You need to run a cross-SDK parity audit for survey integrations before a release to reduce integration risk. Running the audit confirms that surveyVersionRequirements are consistently implemented across all supported platforms and documents any gaps as GitHub issues.

Why does the survey SDK audit use the browser reference implementation?

The survey SDK audit uses the browser reference implementation to drive checks because it serves as the baseline for cross-SDK consistency. It enforces inspection of changelogs and code history to ensure feature support is validated across posthog-js, posthog-ios, posthog-android, and posthog-flutter.

What's the best way to track SDK parity gaps for PostHog surveys?

The best way to track SDK parity gaps for PostHog surveys is to run this audit to generate a structured parity report. The audit outputs structured metadata specifically formatted for GitHub issue creation, ensuring identified gaps across all SDKs are documented and actionable.