๐Ÿ“… let's chat! explore the endless possibilities creating industries that don't exist. click here

posthog-ci-integration

Configure PostHog CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating PostHog tests into your build process. Trigger with phrases like "posthog CI", "posthog GitHub Actions", "posthog automated tests", "CI posthog". allowed-tools: Read, Write, Edit, Bash(gh:*) version: 1.0.0 license: MIT author: Jeremy Longshore <jeremy@intentsolutions.io>

Allowed Tools

No tools specified

Provided by Plugin

posthog-pack

Claude Code skill pack for PostHog (24 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the posthog-pack plugin:

/plugin install posthog-pack@claude-code-plugins-plus

Click to copy

Instructions

# PostHog CI Integration ## Overview Set up CI/CD pipelines for PostHog integrations with automated testing. ## Prerequisites - GitHub repository with Actions enabled - PostHog test API key - npm/pnpm project configured ## Instructions ### Step 1: Create GitHub Actions Workflow Create `.github/workflows/posthog-integration.yml`: ```yaml name: PostHog Integration Tests on: push: branches: [main] pull_request: branches: [main] env: POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY }} jobs: test: runs-on: ubuntu-latest env: POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY }} steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: '20' cache: 'npm' - run: npm ci - run: npm test -- --coverage - run: npm run test:integration ``` ### Step 2: Configure Secrets ```bash gh secret set POSTHOG_API_KEY --body "sk_test_***" ``` ### Step 3: Add Integration Tests ```typescript describe('PostHog Integration', () => { it.skipIf(!process.env.POSTHOG_API_KEY)('should connect', async () => { const client = getPostHogClient(); const result = await client.healthCheck(); expect(result.status).toBe('ok'); }); }); ``` ## Output - Automated test pipeline - PR checks configured - Coverage reports uploaded - Release workflow ready ## Error Handling | Issue | Cause | Solution | |-------|-------|----------| | Secret not found | Missing configuration | Add secret via `gh secret set` | | Tests timeout | Network issues | Increase timeout or mock | | Auth failures | Invalid key | Check secret value | ## Examples ### Release Workflow ```yaml on: push: tags: ['v*'] jobs: release: runs-on: ubuntu-latest env: POSTHOG_API_KEY: ${{ secrets.POSTHOG_API_KEY_PROD }} steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: '20' - run: npm ci - name: Verify PostHog production readiness run: npm run test:integration - run: npm run build - run: npm publish ``` ### Branch Protection ```yaml required_status_checks: - "test" - "posthog-integration" ``` ## Resources - [GitHub Actions Documentation](https://docs.github.com/en/actions) - [PostHog CI Guide](https://docs.posthog.com/ci) ## Next Steps For deployment patterns, see `posthog-deploy-integration`.

Skill file: plugins/saas-packs/posthog-pack/skills/posthog-ci-integration/SKILL.md