[CI] (0ae2102) nuxt/movies-nuxt-3-6

[wizard-ci-bot]

Automated wizard CI run

Source: wizard-pr
Trigger ID: 0ae2102
App: nuxt/movies-nuxt-3-6
App directory: apps/nuxt/movies-nuxt-3-6
Workbench branch: wizard-ci-0ae2102-nuxt-movies-nuxt-3-6
Wizard branch: release-please--branches--main--components--wizard
Context Mill branch: main
PostHog (MCP) branch: master
Timestamp: 2026-04-15T19:23:02.625Z
Duration: 183.4s

[wizard-ci-bot]

Good — .env is in .gitignore so it's not committed. Now I have all the information I need to write the evaluation.

---

PR Evaluation Report

Summary

This PR adds PostHog integration to a Nuxt 3 movies app by installing posthog-js, creating a client-side plugin (posthog.client.ts) that initializes PostHog using runtime config, and adding manual SPA pageview tracking via the Vue Router. The integration is clean and minimal, but lacks identify(), error tracking, a reverse proxy, custom event captures beyond pageviews, and no .env.example file is provided for env var documentation.

Files changed	Lines added	Lines removed
3	+32	-0

Confidence score: 3/5 🤔

• **No custom capture() calls beyond **: The only `posthog.capture()` call is for the built-in event. There are no custom event captures for meaningful user actions (e.g., movie clicks, searches, favorites). [MEDIUM]
• No identify() implementation: There is no posthog.identify() call anywhere, nor a posthog.reset() on logout. While this movie app may not have auth, the integration is incomplete for user identification. [MEDIUM]
• No error tracking: No captureException() or exception autocapture configuration is set up. [MEDIUM]
• No .env.example file: The .env is gitignored (correctly), but there's no .env.example documenting the required NUXT_PUBLIC_POSTHOG_PUBLIC_KEY and NUXT_PUBLIC_POSTHOG_HOST variables for other developers. The runtime config defaults to empty strings, which provides some documentation, but an .env.example is the standard practice. [MEDIUM]
• No reverse proxy configured: No reverse proxy is set up to route PostHog requests through the app's domain, which means ad blockers will block tracking in the browser. [MEDIUM]

---

File changes

Filename	Score	Description
plugins/posthog.client.ts	3/5	New client plugin that initializes PostHog with runtime config, sets up manual pageview capture via router afterEach hook. Clean implementation but lacks identify, error tracking, and custom events.
nuxt.config.ts	4/5	Adds posthogPublicKey and posthogHost to runtimeConfig.public with empty string defaults — correct Nuxt pattern for env vars.
package.json	4/5	Adds posthog-js ^1.369.0 as a dependency. Correctly placed in dependencies (not devDependencies).

---

App sanity check ⚠️

Criteria	Result	Description
App builds and runs	Yes	No syntax errors, valid Nuxt plugin structure, correct package.json format
Preserves existing env vars & configs	Yes	Existing apiBaseUrl runtime config preserved; only additive changes to nuxt.config.ts
No syntax or type errors	Yes	TypeScript is valid; defineNuxtPlugin, useRuntimeConfig, useRouter, nextTick are all auto-imported Nuxt composables
Correct imports/exports	Yes	posthog-js imported correctly for browser-side use; .client.ts suffix ensures it only runs client-side
Minimal, focused changes	Yes	Only 3 files changed, all directly related to PostHog integration
Pre-existing issues	None	Base app appears functional

Issues

• No .env.example file: The runtime config in nuxt.config.ts defaults to empty strings, which partially documents the variables, but there is no .env.example file to communicate the required NUXT_PUBLIC_POSTHOG_PUBLIC_KEY and NUXT_PUBLIC_POSTHOG_HOST environment variables. [MEDIUM]

Other completed criteria

• Build configuration is valid — package.json is well-formed with the new dependency section
• All changes are relevant to PostHog integration
• Code follows existing codebase patterns (Nuxt plugin conventions, runtime config usage)

---

PostHog implementation ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js ^1.369.0 added to dependencies in package.json
PostHog client initialized	Yes	posthog.init() called with runtime config key and host, person_profiles: 'identified_only', manual pageview disabled, debug mode in development
capture()	No	Only `` is captured — no custom user action events
identify()	No	No posthog.identify() or posthog.reset() calls anywhere
Error tracking	No	No captureException() or capture_exceptions config option
Reverse proxy	No	No reverse proxy configured (no Nitro proxy route or similar)

Issues

• No custom capture() calls: The only posthog.capture() is for ``. A movies app should capture events like movie_clicked, `search_performed`, `movie_added_to_watchlist`, etc. to enable meaningful product analytics. [MEDIUM]
• No identify() implementation: No user identification is implemented. Even if the app currently lacks auth, a skeleton identify() pattern should be provided, or this should be explicitly documented as a TODO. [MEDIUM]
• No error tracking: No captureException() usage or capture_exceptions: true in the init config. This is a missed opportunity for error visibility. [MEDIUM]
• No reverse proxy: Browser-side PostHog calls will be blocked by ad blockers. A Nitro server route could proxy requests to us.i.posthog.com. [MEDIUM]

Other completed criteria

• API key loaded from environment variable via Nuxt runtime config (NUXT_PUBLIC_POSTHOG_PUBLIC_KEY)
• API host correctly configured via environment variable (NUXT_PUBLIC_POSTHOG_HOST → https://us.i.posthog.com)
• Client-side only execution ensured by .client.ts plugin suffix
• Manual pageview capture correctly implemented with router.afterEach + nextTick
• person_profiles: 'identified_only' is a good practice for cost optimization
• Debug mode enabled in development

---

PostHog insights and events ⚠️

Filename	PostHog events	Description
plugins/posthog.client.ts	``	Manual pageview capture on route changes with current_url property. Enables basic page analytics.

Issues

• No custom events for product insights: Only `` is captured. This limits analytics to page-level metrics only — no funnels, no user action tracking, no product behavior insights are possible. A movies app should track interactions like viewing movie details, searching, filtering, etc. [MEDIUM]
• Limited event properties: The `` event only includes current_url. While PostHog auto-captures some context, additional properties like page title or movie category could enrich analytics. [LOW]

Other completed criteria

• `` event name follows PostHog conventions
• No PII in event properties (only current_url which is a URL path)
• Event naming is consistent with PostHog standards

---

Reviewed by wizard workbench PR evaluator