Repository navigation
[CI] (3f39e0e) next-js/15-pages-router-todo - #4165
Closed
wizard-ci-bot[bot] wants to merge 1 commit into
Closed
wizard-ci-bot[bot] wants to merge 1 commit into
wizard-ci-bot[bot] wants to merge 1 commit into
Conversation
Author
|
Now I have all the context I need. Let me produce the evaluation. PR Evaluation ReportSummaryThis PR integrates PostHog into a Next.js 15 Pages Router todo app. It adds client-side initialization via
Confidence score: 3/5 🤔
File changes
App sanity check ❌
Issues
|
| Criteria | Result | Description |
|---|---|---|
| PostHog SDKs installed | Yes | posthog-js and posthog-node added to package.json |
| PostHog client initialized | Yes | posthog.init() in instrumentation-client.ts with env vars and capture_exceptions: true |
| capture() | Yes | Three client-side events: todo_created, todo_completion_changed, todo_deleted |
| identify() | No | No posthog.identify() or posthog.reset() calls anywhere in the app |
| Error tracking | Yes | Custom ErrorBoundary with posthog.captureException() and capture_exceptions: true in init |
| Reverse proxy | No | No Next.js rewrites or middleware proxy configured |
Issues
- No user identification: The app has no
posthog.identify()call. All events are captured with anonymous IDs that can never be linked to a known user. There is also noposthog.reset()on logout. For a full-stack Next.js app, this is a significant gap. Fix: addposthog.identify(userId, { email, name })after login/auth andposthog.reset()on logout. [CRITICAL] - No reverse proxy: No Next.js rewrites or middleware configured to proxy PostHog requests. Client-side events will be blocked by ad blockers. Fix: add rewrites in
next.config.jsor use PostHog's managed reverse proxy. [MEDIUM] - Server-side uses OTEL logs instead of PostHog events: The API routes emit OTEL logs to PostHog's log endpoint, but these are not proper PostHog analytics events. They cannot be used in funnels, trends, or retention charts. The installed
posthog-nodepackage is never used. Fix: useposthog-nodetocapture()server-side events instead of OTEL logs. [MEDIUM]
Other completed criteria
- API key loaded from
NEXT_PUBLIC_POSTHOG_PROJECT_TOKENenvironment variable - API host loaded from
NEXT_PUBLIC_POSTHOG_HOSTenvironment variable instrumentation-client.tsis the correct file for Next.js client-side initialization- Error boundary properly wraps the app in
_app.tsx
PostHog insights and events ⚠️
| Filename | PostHog events | Description |
|---|---|---|
components/todos/todo-list.tsx |
todo_created, todo_completion_changed, todo_deleted |
Client-side captures for core CRUD actions on todos |
components/ErrorBoundary.tsx |
captureException |
Captures React component errors with component stack traces |
instrumentation-client.ts |
autocaptured events | capture_exceptions: true enables automatic exception tracking |
lib/posthog-logs.ts |
OTEL logs (not PostHog events) | Server-side OTEL log emissions — these are logs, not analytics events |
Issues
todo_deletedhas no properties: Thetodo_deletedevent is captured with zero properties, making it impossible to analyze what was deleted or the context around deletion. Fix: add relevant properties liketodo_idorwas_completed. [MEDIUM]- Server-side operations only emit logs, not events: Todo CRUD on the server side emits OTEL logs that won't appear in PostHog's event stream. You cannot build funnels with client + server events because the server-side "events" are logs. [MEDIUM]
Other completed criteria
- Events represent real user actions (creating, completing, deleting todos)
- Client-side events enable basic product insights (can build a funnel: create → complete → delete)
- No PII in event properties
- Event names use descriptive snake_case convention
Reviewed by wizard workbench PR evaluator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Automated wizard CI run
Source: wizard-pr
Trigger ID:
3f39e0eApp:
next-js/15-pages-router-todoApp directory:
apps/next-js/15-pages-router-todoWorkbench branch:
wizard-ci-3f39e0e-next-js-15-pages-router-todoWizard branch:
release-please--branches--main--components--wizardContext Mill branch:
mainPostHog (MCP) branch:
masterTimestamp: 2026-09-23T22:10:01.728Z
Duration: 519.1s
YARA Scanner