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

[wizard-ci-bot]

Automated wizard CI run

Trigger ID: 5564901
App: next-js/15-app-router-todo
App directory: apps/next-js/15-app-router-todo
Workbench branch: wizard-ci-5564901-next-js-15-app-router-todo
Wizard branch: main
Examples branch: main
PostHog (MCP) branch: master
Timestamp: 2026-01-14T16:11:30.498Z
Duration: 215.9s

[wizard-ci-bot]

Now I have all the context I need. Let me compile the PR evaluation report.

---

PR Evaluation Report

Summary

This PR adds PostHog analytics integration to a Next.js 15 Todo application. It implements client-side initialization via instrumentation-client.ts, configures a reverse proxy to avoid ad blockers, adds event tracking for all CRUD operations on todos, and includes error tracking with captureException.

Files changed	Lines added	Lines removed
6	+463	-2

Confidence score: 3/5 🤔

• Missing identify() call: No user identification is implemented, meaning all events are anonymous. This significantly limits analytics value for user-level insights. [MEDIUM]
• Missing pageview tracking: No explicit pageview/screen tracking configured. The defaults: '2025-05-24' option may enable autocapture, but explicit pageview tracking would be more reliable. [MEDIUM]
• .env file not in diff but contains secrets: The .env file with PostHog API key exists but wasn't included in the PR diff - this is inconsistent with the report claiming it was created. The key sTMFPsFhdP1Ssg appears to be a placeholder/test key (unusually short). [LOW]

---

File changes

Filename	Score	Description
components/todos/todo-list.tsx	4/5	Adds PostHog import and capture calls for CRUD operations with error tracking. Clean integration preserving original functionality.
instrumentation-client.ts	4/5	New file for PostHog client initialization using the recommended Next.js 15.3+ pattern. Uses reverse proxy path /ingest.
next.config.ts	5/5	Adds reverse proxy rewrites for PostHog and skipTrailingSlashRedirect. Correct configuration.
package.json	5/5	Adds posthog-js dependency. Clean addition.
pnpm-lock.yaml	5/5	Lock file updated with PostHog and its dependencies.
posthog-setup-report.md	4/5	Documentation of the integration. Minor inaccuracy: claims .env was created but it's not in the diff.

---

App sanity check: 4/5 ✅

Criteria	Result	Description
App builds and runs	Yes	No syntax errors, correct imports, proper TypeScript usage
Preserves existing env vars & configs	Yes	Original next.config.ts structure preserved, new configs added cleanly
No syntax or type errors	Yes	All TypeScript compiles correctly, proper type handling for errors
Correct imports/exports	Yes	posthog-js imported correctly as default export
Minimal, focused changes	Yes	Only PostHog-related changes, no unrelated modifications

Issues

• Environment variable documentation incomplete: The .env file exists but wasn't included in the PR diff, making it unclear if this was pre-existing or created. Should have .env.example for documentation. [LOW]

Other completed criteria

• Error handling preserved with console.error calls
• Original component logic unchanged
• Clean code additions following existing patterns
• No PII exposed in event properties

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.321.1 added to dependencies
PostHog client initialized	Yes	Via instrumentation-client.ts with api_host: "/ingest" and capture_exceptions: true
capture()	Yes	Events captured for create, complete, uncomplete, delete, and all error states
identify()	No	No user identification implemented - all events are anonymous
Error tracking	Yes	Both custom error events (*_error) and captureException() calls implemented
Reverse proxy	Yes	Correctly configured in next.config.ts with /ingest path to US PostHog servers

Issues

• No user identification: Missing posthog.identify() call. Without this, all analytics are anonymous and you cannot track individual user journeys or segment by user properties. [MEDIUM]
• No explicit pageview tracking: Relies on defaults: '2025-05-24' option which may enable autocapture, but explicit pageview tracking is not implemented. [MEDIUM]
• defaults option value suspicious: The value '2025-05-24' is a non-standard option format. PostHog defaults should be an object like { person_profiles: 'identified_only' }, not a date string. This may cause initialization issues or be silently ignored. [MEDIUM]

Other completed criteria

• Proper API host configuration using reverse proxy
• Debug mode enabled only in development
• Exception capture enabled via capture_exceptions: true
• No PII in captured event properties
• Comment warning against duplicate PostHog initialization

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
todo-list.tsx	todo_created	Tracks when a todo is created with todo_id and has_description properties
todo-list.tsx	todo_completed	Tracks when a todo is marked complete with todo_id
todo-list.tsx	todo_uncompleted	Tracks when a todo is marked incomplete with todo_id
todo-list.tsx	todo_deleted	Tracks when a todo is deleted with todo_id
todo-list.tsx	todo_fetch_error, todo_create_error, todo_update_error, todo_delete_error	Error events with error_message property
todo-list.tsx	captureException	Exception capture for all error catch blocks

Issues

• Events lack timestamp context: No properties indicating time spent on task or time to completion. [LOW]
• No session-level context: Events don't include list size, position in list, or batch operation context. [LOW]

Other completed criteria

• Events represent real user actions (CRUD operations)
• Events can build funnels (create → complete → delete)
• Error tracking enables error rate monitoring
• Properties enriched with relevant IDs and metadata
• Events properly differentiate success vs error states

---

Reviewed by wizard workbench PR evaluator