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

[wizard-ci-bot]

Automated wizard CI run

Trigger ID: bd496c4
App: next-js/15-app-router-todo
App directory: apps/next-js/15-app-router-todo
Workbench branch: wizard-ci-bd496c4-next-js-15-app-router-todo
Wizard branch: main
Examples branch: rearchitect-generator
PostHog (MCP) branch: master
Timestamp: 2026-01-14T16:16:53.869Z
Duration: 274.4s

[wizard-ci-bot]

Now I have all the context needed to provide a comprehensive evaluation. Let me compile the PR review:

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a Next.js 15 App Router todo application. It adds client-side initialization via instrumentation-client.ts, server-side PostHog client setup, reverse proxy configuration for ad-block circumvention, and comprehensive event tracking for all CRUD operations on todos. A reusable TrackedLink component was created for navigation tracking.

Files changed	Lines added	Lines removed
10	+532	-5

Confidence score: 3/5 🤔

• Invalid PostHog initialization option: The defaults: '2025-05-24' option in instrumentation-client.ts is not a valid PostHog configuration option. This should be removed or replaced with valid options. [CRITICAL]
• Missing .env.example file: The .env file containing actual API keys is committed to the PR diff but there's no .env.example template for other developers. The committed .env exposes what appears to be a real API key. [MEDIUM]
• Server-side client created but unused: lib/posthog-server.ts is created but never imported or used anywhere in the application. This is dead code. [MEDIUM]

---

File changes

Filename	Score	Description
app/about/page.tsx	4/5	Replaced Link with TrackedLink component to track navigation. Clean change, preserves existing structure.
components/todos/todo-form.tsx	4/5	Added PostHog import and form submission tracking with useful properties (has_description, title_length).
components/todos/todo-list.tsx	4/5	Comprehensive event tracking for all CRUD operations with error tracking via captureException. Well-structured.
components/tracked-link.tsx	4/5	New reusable component for tracked navigation links. Clean implementation with TypeScript types.
instrumentation-client.ts	2/5	Uses invalid defaults configuration option. Otherwise follows correct Next.js 15.3+ pattern.
lib/posthog-server.ts	3/5	Server-side client setup is correct but the file is never used anywhere in the application.
next.config.ts	5/5	Properly configured reverse proxy rewrites for PostHog to circumvent ad blockers.
package.json	5/5	Both posthog-js and posthog-node dependencies added with appropriate versions.
pnpm-lock.yaml	5/5	Lock file properly updated with new dependencies.
posthog-setup-report.md	4/5	Good documentation of the integration, but the API key shown should use placeholder values.

---

App sanity check: 3/5 ⚠️

Criteria	Result	Description
App builds and runs	Uncertain	Invalid defaults option in PostHog init may cause runtime warnings or errors
Preserves existing env vars & configs	Yes	Original app functionality is preserved, only PostHog additions made
No syntax or type errors	Yes	TypeScript types are correct, imports are properly structured
Correct imports/exports	Yes	All imports resolve correctly, components properly exported
Minimal, focused changes	Yes	Changes are focused on PostHog integration only

Issues

• Invalid PostHog configuration: The defaults: '2025-05-24' option in instrumentation-client.ts is not a valid PostHog initialization option. This will likely be ignored but indicates a misunderstanding of the API. Should be removed. [CRITICAL]
• API key committed to repository: The .env file with what appears to be a real PostHog API key (sTMFPsFhdP1Ssg) is committed. Should use .env.example with placeholder values instead. [MEDIUM]
• Dead code: lib/posthog-server.ts is created but never imported or used. [MEDIUM]

Other completed criteria

• Existing UI components and logic preserved
• TypeScript types properly defined
• No breaking changes to existing functionality
• Clean code organization following project patterns

---

PostHog implementation: 4/5 ✅

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js v1.321.1 and posthog-node v5.21.0 added to dependencies
PostHog client initialized	Partial	Client initialized via instrumentation-client.ts (correct for Next.js 15.3+) but with invalid defaults option
capture()	Yes	Used correctly throughout todo-list.tsx and todo-form.tsx for all user actions
identify()	No	No user identification implemented (acceptable for anonymous tracking)
Error tracking	Yes	posthog.captureException() used in all catch blocks, plus capture_exceptions: true enabled
Reverse proxy	Yes	Properly configured in next.config.ts with /ingest rewrites to PostHog CDN

Issues

• Invalid defaults option: The defaults: '2025-05-24' is not a valid PostHog configuration property. This should be removed from instrumentation-client.ts. [CRITICAL]
• Server-side client unused: posthog-node is installed and lib/posthog-server.ts is created, but no server-side tracking is actually implemented. [LOW]
• No user identification: While acceptable for anonymous tracking, posthog.identify() is not implemented for authenticated users. [LOW]

Other completed criteria

• API host correctly configured via reverse proxy (/ingest)
• ui_host set to https://us.posthog.com
• Debug mode enabled in development
• capture_exceptions: true for automatic error tracking
• Environment variables properly namespaced with NEXT_PUBLIC_ prefix
• skipTrailingSlashRedirect: true configured for PostHog API compatibility

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
todo-form.tsx	todo_form_submitted	Tracks form submissions with properties: has_description, title_length
todo-list.tsx	todo_created, todo_completed, todo_uncompleted, todo_deleted, about_page_link_clicked, api_error_occurred	Comprehensive CRUD tracking with relevant properties (todo_id, total_todos, remaining_todos, action, error_message)
about/page.tsx	back_to_todos_clicked	Navigation tracking via TrackedLink component
instrumentation-client.ts	captureException (automatic)	Automatic unhandled exception capture enabled

Issues

• Redundant form/creation events: todo_form_submitted and todo_created both fire on successful todo creation. Consider whether both are needed or consolidate into one. [LOW]

Other completed criteria

• Events capture real user actions (create, complete, delete todos)
• Events enriched with relevant properties for analysis
• Error tracking includes action context and error messages
• Navigation events enable user journey analysis
• Properties avoid PII (no user-entered content captured)
• Events support funnel analysis (form → create → complete)
• Events support trend analysis (CRUD operations over time)

---

Reviewed by wizard workbench PR evaluator