[CI] (8ac6d56) next-js/15-pages-router-todo

[wizard-ci-bot]

Automated wizard CI run

Trigger ID: 8ac6d56
App: next-js/15-pages-router-todo
App directory: apps/next-js/15-pages-router-todo
Workbench branch: wizard-ci-8ac6d56-next-js-15-pages-router-todo
Wizard branch: feat-skill-based-integration
Examples branch: test-skills-ci
PostHog (MCP) branch: feat-mcp-skill-deployment
Timestamp: 2026-01-14T21:24:57.294Z
Duration: 251.9s

[wizard-ci-bot]

Now I have all the information needed to write the comprehensive PR evaluation report.

---

PR Evaluation Report

Summary

This PR integrates PostHog analytics into a Next.js 15 Pages Router todo application. It adds client-side initialization via instrumentation-client.ts, server-side PostHog client setup, reverse proxy configuration for ad-blocker bypass, and event tracking for todo CRUD operations with error capture.

Files changed	Lines added	Lines removed
7	+508	-2

Confidence score: 2/5 ❌

• Debug comment pollution: Every modified file contains // MEEEEOWWW IM A DOG comment at the top, which is unprofessional and should not be in production code [CRITICAL]
• Incorrect initialization approach for Pages Router: instrumentation-client.ts is designed for Next.js 15 App Router, but this is a Pages Router app. The client-side PostHog should be initialized in _app.tsx using useEffect or a provider pattern [CRITICAL]
• Missing pageview tracking: No automatic pageview capture is implemented. Pages Router apps require manual posthog.capture('') on route changes via Router.events [CRITICAL]
• Missing user identification: No posthog.identify() implementation for user tracking [MEDIUM]
• Unused server-side client: lib/posthog-server.ts is created but never used anywhere in the codebase [MEDIUM]

---

File changes

Filename	Score	Description
components/todos/todo-list.tsx	3/5	Adds PostHog import and event tracking for CRUD operations with error handling. Contains debug comment.
instrumentation-client.ts	2/5	New file for PostHog initialization. Wrong approach for Pages Router - this pattern is for App Router. Contains debug comment and uses defaults option incorrectly (should be object, not string).
lib/posthog-server.ts	2/5	Server-side client setup with singleton pattern. Never used in codebase. Contains debug comment.
next.config.ts	4/5	Properly configured reverse proxy rewrites for PostHog. Contains debug comment.
package.json	5/5	Correctly adds posthog-js and posthog-node dependencies.
pnpm-lock.yaml	5/5	Lock file updated correctly with PostHog dependencies and transitive deps.
posthog-setup-report.md	3/5	Documentation file claims .env was created but env vars are committed to repo (security concern).

---

App sanity check: 3/5 ⚠️

Criteria	Result	Description
App builds and runs	Yes	Build completes successfully with next build
Preserves existing env vars & configs	Partial	Added reactStrictMode: true which wasn't there before; original config preserved
No syntax or type errors	Yes	TypeScript compilation passes
Correct imports/exports	Yes	All imports resolve correctly
Minimal, focused changes	No	Debug comments in every file; unused server client; unnecessary documentation file

Issues

• Debug comments in all files: Every modified/created file contains // MEEEEOWWW IM A DOG which is unprofessional debugging artifact that should not be shipped. Remove these comments. [CRITICAL]
• Unused code: lib/posthog-server.ts is created but never imported or used anywhere. Either remove or demonstrate usage. [MEDIUM]
• Environment variables in report: The setup report exposes NEXT_PUBLIC_POSTHOG_KEY value which, while public keys, is still a questionable practice to commit. [LOW]

Other completed criteria

• TypeScript types are correct
• Import paths use @/ alias correctly
• Error handling patterns are consistent
• Build output shows no warnings related to PostHog integration

---

PostHog implementation: 2/5 ❌

Criteria	Result	Description
PostHog SDKs installed	Yes	posthog-js@1.321.2 and posthog-node@5.21.0 added
PostHog client initialized	Partial	Uses instrumentation-client.ts which is App Router pattern, not Pages Router
capture()	Yes	Events captured for todo create, complete, uncomplete, delete, and failures
identify()	No	No user identification implemented
Error tracking	Yes	captureException() called on all catch blocks
Reverse proxy	Yes	Properly configured in next.config.ts with /ingest rewrites

Issues

• Wrong initialization pattern for Pages Router: instrumentation-client.ts is the Next.js 15.3+ App Router approach. For Pages Router, PostHog should be initialized in _app.tsx with a useEffect hook or using PostHogProvider. The current implementation may not work correctly or may initialize PostHog multiple times. [CRITICAL]
• Missing pageview tracking: Pages Router requires manual pageview tracking on route changes using Router.events.on('routeChangeComplete', ...). Automatic pageview capture won't work correctly without this. [CRITICAL]
• Invalid defaults option: The defaults: '2025-05-24' in initialization should be an object with configuration options, not a string date. This is incorrect API usage. [MEDIUM]
• No user identification: posthog.identify() is not called anywhere, meaning all events will be anonymous and harder to correlate. [MEDIUM]
• Server client unused: posthog-node is installed and configured but never actually used for server-side tracking. [MEDIUM]

Other completed criteria

• API host correctly points to /ingest proxy
• UI host configured for US region
• capture_exceptions: true enabled
• Debug mode enabled for development
• Environment variables properly prefixed with NEXT_PUBLIC_

---

PostHog insights and events: 3/5 ⚠️

Filename	PostHog events	Description
todo-list.tsx	todo_created	Captures when user creates a todo with todo_id, has_description, total_todos properties
todo-list.tsx	todo_completed, todo_uncompleted	Tracks toggle state changes with todo_id
todo-list.tsx	todo_deleted	Captures deletion with todo_id, remaining_todos
todo-list.tsx	todos_fetch_failed, todo_create_failed, todo_update_failed, todo_delete_failed	Error events with error message properties
instrumentation-client.ts	captureException	Automatic exception capture enabled via capture_exceptions: true

Issues

• Missing pageview events: No `` events are being captured. This is critical for understanding user journeys and sessions. [CRITICAL]
• No session recording context: Without proper initialization in Pages Router, session replay may not work correctly. [MEDIUM]
• Limited property enrichment: Events could include more context like timestamp, page URL, or todo title (with PII consideration). [LOW]

Other completed criteria

• Events follow consistent naming convention (snake_case)
• Error events include error message safely extracted
• Success events include relevant metadata (counts, IDs)
• No PII exposed in event properties (todo titles not captured)
• Events represent real user actions and product flows

---

Reviewed by wizard workbench PR evaluator