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

[wizard-ci-bot]

Automated wizard CI run

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

[wizard-ci-bot]

The files don't exist at the local path, but I have the complete diff provided in the PR description which contains all the file changes. I can perform a thorough evaluation based on the diff content provided.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a Next.js 15 App Router Todo application. It adds client-side PostHog initialization via instrumentation-client.ts, configures a reverse proxy to avoid ad-blockers, and implements comprehensive event tracking across todo CRUD operations and navigation flows.

Files changed	Lines added	Lines removed
9	+531	-9

Confidence score: 3/5 🤔

• Invalid defaults option: The instrumentation-client.ts uses defaults: '2025-05-24' which is not a valid PostHog configuration option. This should be removed or corrected. [CRITICAL]
• Missing .env file in PR: The report references environment variables in .env but the file is not included in the PR diff, leaving NEXT_PUBLIC_POSTHOG_KEY undefined at runtime. [CRITICAL]
• No user identification: No posthog.identify() calls are implemented, limiting user-level analytics capabilities. [MEDIUM]
• Event duplication: todo_form_submitted in todo-form.tsx and todo_created in todo-list.tsx capture overlapping data for the same user action. [LOW]

---

File changes

Filename	Score	Description
app/about/page.tsx	4/5	Clean refactor replacing inline Link with tracked BackToTodosLink component. Maintains existing styling and functionality.
components/back-to-todos-link.tsx	4/5	New client component wrapping Link with PostHog tracking. Well-structured with 'use client' directive.
components/todos/todo-form.tsx	4/5	Adds form submission tracking with useful properties (title/description length). Clean integration.
components/todos/todo-list.tsx	4/5	Comprehensive event tracking for all CRUD operations with error handling via captureException. Good property enrichment.
instrumentation-client.ts	2/5	Invalid defaults option will cause issues. Otherwise follows Next.js 15.3+ recommended pattern.
next.config.ts	5/5	Correct reverse proxy setup for PostHog with proper asset and API routing. Includes skipTrailingSlashRedirect.
package.json	5/5	posthog-js dependency added correctly.
pnpm-lock.yaml	5/5	Lock file properly updated with PostHog and OpenTelemetry dependencies.
posthog-setup-report.md	4/5	Helpful documentation but references a .env file not in the PR and contains a truncated/invalid API key.

---

App sanity check: 3/5 ⚠️

Criteria	Result	Description
App builds and runs	Uncertain	Invalid defaults option in PostHog init may cause runtime errors
Preserves existing env vars & configs	Yes	Only additive changes to next.config.ts
No syntax or type errors	Yes	TypeScript appears correct throughout
Correct imports/exports	Yes	All imports are valid; posthog-js imported correctly
Minimal, focused changes	Yes	Changes are scoped to PostHog integration only

Issues

• Invalid PostHog configuration: defaults: '2025-05-24' is not a valid PostHog option. This should be removed from instrumentation-client.ts. [CRITICAL]
• Missing .env file: Environment variables NEXT_PUBLIC_POSTHOG_KEY and NEXT_PUBLIC_POSTHOG_HOST are referenced but not included in the PR. Without these, PostHog will not initialize. [CRITICAL]
• Truncated API key in report: The posthog-setup-report.md shows NEXT_PUBLIC_POSTHOG_KEY=sTMFPsFhdP1Ssg which appears truncated (PostHog keys are typically longer). [MEDIUM]

Other completed criteria

• Code follows existing patterns in the codebase
• No unnecessary modifications to existing logic
• Proper error handling with try/catch blocks preserved
• TypeScript types used correctly (e.g., Todo type in filters)

---

PostHog implementation: 3/5 ⚠️

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@^1.321.1 added to dependencies
PostHog client initialized	Partial	Initialized in instrumentation-client.ts but with invalid defaults option
capture()	Yes	Comprehensive event capturing across todo operations
identify()	No	No user identification implemented
Error tracking	Yes	capture_exceptions: true enabled; captureException() called on errors
Reverse proxy	Yes	Proper rewrites configured in next.config.ts for /ingest routes

Issues

• Invalid defaults option: The defaults: '2025-05-24' is not a recognized PostHog configuration option and should be removed. [CRITICAL]
• No user identification: Without posthog.identify(), all events are anonymous. Should identify users when they have a session or user context. [MEDIUM]
• No automatic pageview tracking: capture_pageview is not explicitly configured. Consider enabling for automatic page tracking. [LOW]

Other completed criteria

• Correct API host configuration via reverse proxy (/ingest)
• UI host properly set to https://us.posthog.com
• Debug mode enabled in development
• Exception capture enabled
• No PII in event properties (only lengths and IDs tracked)

---

PostHog insights and events: 4/5 ✅

Filename	PostHog events	Description
todo-list.tsx	todos_loaded, todos_load_failed, todo_created, todo_create_failed, todo_completed, todo_uncompleted, todo_deleted, todo_delete_failed, todo_update_failed, about_page_link_clicked	Comprehensive CRUD tracking with counts, completion states, and error capture
todo-form.tsx	todo_form_submitted	Form submission with metadata (has_description, lengths)
back-to-todos-link.tsx	back_to_todos_clicked	Navigation tracking from About page
todo-list.tsx	captureException	Error tracking for all failed API operations

Issues

• Duplicate tracking for todo creation: Both todo_form_submitted (in form) and todo_created (in list) fire for the same action. Consider consolidating or ensuring distinct purposes. [LOW]
• Missing pageview events: No explicit page view tracking for landing on main or about pages. [LOW]

Other completed criteria

• Events capture real user actions (create, complete, delete todos)
• Events include relevant properties for analysis (counts, lengths, completion states)
• Error events include error messages for debugging
• Events enable funnel analysis (form submission → creation)
• Events support cohort analysis (active vs completed todos ratio)
• Navigation flow tracking implemented

---

Reviewed by wizard workbench PR evaluator