[CI] (dabf817) next-js/15-app-router-todo

[wizard-ci-bot]

Automated wizard CI run

Trigger ID: dabf817
App: next-js/15-app-router-todo
App directory: apps/next-js/15-app-router-todo
Workbench branch: wizard-ci-dabf817-next-js-15-app-router-todo
Wizard branch: feat-skill-based-integration
Examples branch: rearchitect-generator
PostHog (MCP) branch: feat-mcp-skill-deployment
Timestamp: 2026-01-14T20:53:38.940Z
Duration: 188.9s

[wizard-ci-bot]

Now I have all the information needed to write a comprehensive evaluation. Let me compile the review:

---

PR Evaluation Report

Summary

This PR adds PostHog analytics integration to a Next.js 15 App Router Todo application. It includes client-side initialization via instrumentation-client.ts, reverse proxy configuration for ad-blocker circumvention, and event tracking for all CRUD operations on todos with error tracking.

Files changed	Lines added	Lines removed
6	+470	-2

Confidence score: 3/5 🤔

• Missing .env.example: The .env file with a real API key was created but no .env.example template was added, which is poor practice for onboarding other developers. [MEDIUM]
• posthog-node installed but unused: The server-side SDK is in dependencies but no server-side tracking is implemented. This adds unnecessary bundle size. [MEDIUM]
• No user identification (identify()): There's no posthog.identify() call to link events to users, limiting analytics value for cohort analysis. [MEDIUM]
• No page view tracking: Automatic pageview capture is not explicitly enabled, and the defaults option appears to be a non-standard configuration option. [LOW]

---

File changes

Filename	Score	Description
components/todos/todo-list.tsx	4/5	Added PostHog import and 8 capture calls for CRUD operations and errors. Clean integration that preserves existing logic.
instrumentation-client.ts	3/5	New file for PostHog initialization using Next.js 15.3+ pattern. Uses non-null assertion on env var without runtime check. defaults option is non-standard.
next.config.ts	5/5	Added reverse proxy rewrites correctly with skipTrailingSlashRedirect flag. Properly preserves original config structure.
package.json	4/5	Added posthog-js and posthog-node. Note: posthog-node is unused in this PR.
pnpm-lock.yaml	5/5	Lock file correctly updated with new dependencies and transitive deps.
posthog-setup-report.md	4/5	Documentation of events and setup. Claims .env was created but no .env.example was provided.

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	Build completes successfully with next build
Preserves existing env vars & configs	Yes	Original next.config.ts structure preserved; no existing env vars overwritten
No syntax or type errors	Yes	TypeScript compilation passes
Correct imports/exports	Yes	PostHog import added correctly at top of file
Minimal, focused changes	Partial	Changes are focused but posthog-node is installed unnecessarily

Issues

• Unused dependency: posthog-node is added to dependencies but not used anywhere in the codebase. This adds unnecessary package weight. Remove from package.json if server-side tracking is not planned. [LOW]
• Non-null assertion risk: process.env.NEXT_PUBLIC_POSTHOG_KEY! uses TypeScript non-null assertion but no runtime validation exists. If env var is missing, PostHog will initialize with undefined. [LOW]

Other completed criteria

• Existing app code structure preserved
• Error handling maintained in all CRUD operations
• No breaking changes to existing functionality
• React patterns followed correctly

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js ^1.321.2 and posthog-node ^5.21.0 added
PostHog client initialized	Yes	Via instrumentation-client.ts with api_host: "/ingest" pointing to reverse proxy
capture()	Yes	8 capture calls for todo CRUD success/error events
identify()	No	No user identification implemented
Error tracking	Partial	capture_exceptions: true enabled but manual error captures don't use captureException
Reverse proxy	Yes	Correctly configured in next.config.ts with rewrites to us.i.posthog.com

Issues

• No posthog.identify() call: User identification is missing. Without this, all events are anonymous and cannot be tied to specific users for cohort analysis or user journeys. [MEDIUM]
• Invalid defaults option: The defaults: '2025-05-24' option in PostHog initialization is not a documented PostHog configuration option. This may be ignored or cause unexpected behavior. [MEDIUM]
• Manual error tracking doesn't use SDK method: Error events are captured with posthog.capture('*_error') instead of using posthog.capture('') or the exception autocapture pattern. While this works, it's inconsistent with the capture_exceptions: true configuration. [LOW]
• No .env.example file: Environment variables are documented in markdown but no .env.example template was created. Other developers won't know which variables are required. [MEDIUM]

Other completed criteria

• API host correctly points to reverse proxy endpoint /ingest
• UI host correctly set to https://us.posthog.com
• Debug mode appropriately enabled only in development
• Reverse proxy handles both static assets and API endpoints
• skipTrailingSlashRedirect: true correctly added for PostHog API compatibility

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
todo-list.tsx	todo_created	Captures todo creation with todo_id and has_description properties
todo-list.tsx	todo_completed, todo_uncompleted	Tracks completion state changes with todo_id
todo-list.tsx	todo_deleted	Captures deletion with todo_id
todo-list.tsx	todo_fetch_error, todo_create_error, todo_update_error, todo_delete_error	Error tracking with error message property
instrumentation-client.ts	`` (autocapture)	Automatic exception capture enabled via config

Issues

• Limited event properties: Events capture todo_id but don't include richer context like todo title length, time since creation for delete events, or session context. This limits insight depth. [LOW]
• No page view tracking events: While capture_exceptions is enabled, explicit pageview tracking (capture_pageview) is not configured, and no manual pageview events exist. [LOW]

Other completed criteria

• Events represent real user actions (create, complete, delete)
• Error events capture meaningful error messages
• Event naming follows consistent snake_case convention
• Events are placed at appropriate success/error boundaries
• No PII captured in event properties

---

Reviewed by wizard workbench PR evaluator