fix: resolve commandment contradictions, install/build edge cases - #277
Draft
posthog[bot] wants to merge 1 commit into
Draft
fix: resolve commandment contradictions, install/build edge cases#277posthog[bot] wants to merge 1 commit into
posthog[bot] wants to merge 1 commit into
Conversation
…e cases Answers three recurring orchestrator remarks from the past cycle: - javascript_node's `enableExceptionAutocapture` bullet was being merged into isomorphic-framework skills (Next.js, Nuxt, SvelteKit, Remix, TanStack Start) alongside javascript_web rules with no scoping, so error-tracking/review runs occasionally tried it on the browser posthog-js client (which has no such option) before self-correcting to `capture_exceptions`. Now scoped explicitly to the server-side posthog-node client. - The generic `python` tag told every Python integration to use the instance-based `Posthog()` client, directly contradicting the `django`, `flask`, and `fastapi` sections (and the actual Django example app), which all correctly use module-level `posthog.api_key` init per PostHog's own docs. Now scoped to plain scripts/CLIs with no framework-specific pattern. - `install` and `build` skills didn't cover two recurring edge cases agents kept flagging: multi-manifest monorepos (JS frontend + Python/PHP backend) and manifests with no build/typecheck/lint script at all (start-only Node projects). Remaining themes from this cycle (task-management tooling not offered to several task types, the PostHog MCP gateway being unreachable in some runs, an environment writer corrupting `.ts` files) are wizard-side or infra issues outside this repo's scope and were left for separate follow-up. `npm test` and `npm run build` pass. --- *Created with [PostHog Code](https://posthog.com/code?ref=pr)* Generated-By: PostHog Code Task-Id: 4e596905-5f12-4c8b-b9bb-56a3a64bd534
🧙 Wizard CIRun the Wizard CI and test your changes against wizard-workbench example apps by replying with a GitHub comment using one of the following commands: Test all apps:
Test all apps in a directory:
Test an individual app:
Show more apps
Results will be posted here when complete. |
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.
Summary
enableExceptionAutocapture(posthog-node-only) was bleeding into isomorphic-framework skills (Next.js, Nuxt, SvelteKit, Remix, TanStack Start) that also carryjavascript_web, since commandments are flattened across tags with no scoping — agents occasionally tried it on the browser posthog-js client before self-correcting tocapture_exceptions. Now the bullet names the client and contrasts it explicitly.pythoncommandment ("always use the instance-basedPosthog()client") directly contradicted thedjango,flask, andfastapisections (and the real Django example app), which all correctly use module-levelposthog.api_keyinit per PostHog's own docs. Now scoped to plain scripts/CLIs with no framework-specific pattern of their own.installandbuildskill descriptions didn't cover two edge cases orchestrator runs kept flagging: multi-manifest monorepos (JS frontend + Python/PHP backend) and manifests with no build/typecheck/lint script (start-only Node projects).Why
Triaged 365 new
wizard: orchestrator remarkevents since the last cycle. Most were confirmations or wizard/infra-side issues (task-management tooling not offered to some task types, the PostHog MCP gateway being unreachable in some runs, a.tsenv-writer bug) outside this repo's scope — left for separate follow-up. These three findings were the ones traceable to actual contradictions/gaps in this repo's content.Test plan
npm testnpm run build(confirmed the renderedCOMMANDMENTS.mdfor a Next.js and a Django skill reflect the fixes)Created with PostHog Code