Skip to content

feat(self-driving): always enable the health checks signal source#196

Draft
rafaeelaudibert wants to merge 1 commit into
mainfrom
posthog-code/self-driving-always-enable-health-checks
Draft

feat(self-driving): always enable the health checks signal source#196
rafaeelaudibert wants to merge 1 commit into
mainfrom
posthog-code/self-driving-always-enable-health-checks

Conversation

@rafaeelaudibert

Copy link
Copy Markdown
Member

What

The self-driving setup skill (context/skills/self-driving/references/4-sources.md, step 4) now enables the health_checks / health_issue signal source always, as a sibling of the always-on scout gate, instead of never turning it on.

Why

Health findings — missing events, proxy gaps, outdated SDKs — are always actionable, and they're a good thing for the agent to fix. Unlike error tracking / session replay / support (which are conditional on the product actually using those surfaces), there's no reason to gate health checks: every project benefits. The source already exists in PostHog; the self-driving flow just wasn't turning it on.

Note on health checks: source vs. scout

These are complementary, not redundant:

  • signals-scout-health-checks (step 6) is the always-on scout whose findings reach the inbox via the scout gate.
  • health_checks / health_issue (this change, step 4) is the native inbox source ("Responder").

Adding the source closes a real gap — it isn't covered by the scout being on.

Reference bodies are copied verbatim at build time, so this is a direct markdown edit with no codegen.

🤖 Generated with Claude Code

Health findings — missing events, proxy gaps, outdated SDKs — are always
actionable and a good fix target for the agent, so the self-driving setup now
treats the `health_checks` / `health_issue` source as always-on alongside the
scout gate, rather than leaving it off. Adds it as a sibling always-on row in
step 4's Enable table.

Generated-By: PostHog Code
Task-Id: f43da6e8-ca5d-4ae0-8451-e6cce79e4e85
@github-actions

Copy link
Copy Markdown

🧙 Wizard CI

Run 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:

  • /wizard-ci all

Test all apps in a directory:

  • /wizard-ci basic-integration
  • /wizard-ci error-tracking-upload-source-maps
  • /wizard-ci misc
  • /wizard-ci revenue

Test an individual app:

  • /wizard-ci basic-integration/android
  • /wizard-ci basic-integration/angular
  • /wizard-ci basic-integration/astro
Show more apps
  • /wizard-ci basic-integration/django
  • /wizard-ci basic-integration/fastapi
  • /wizard-ci basic-integration/flask
  • /wizard-ci basic-integration/javascript-node
  • /wizard-ci basic-integration/javascript-web
  • /wizard-ci basic-integration/laravel
  • /wizard-ci basic-integration/next-js
  • /wizard-ci basic-integration/nuxt
  • /wizard-ci basic-integration/python
  • /wizard-ci basic-integration/rails
  • /wizard-ci basic-integration/react-native
  • /wizard-ci basic-integration/react-router
  • /wizard-ci basic-integration/sveltekit
  • /wizard-ci basic-integration/swift
  • /wizard-ci basic-integration/tanstack-router
  • /wizard-ci basic-integration/tanstack-start
  • /wizard-ci basic-integration/vue
  • /wizard-ci error-tracking-upload-source-maps/android
  • /wizard-ci error-tracking-upload-source-maps/cicd-docker-node-raw
  • /wizard-ci error-tracking-upload-source-maps/cicd-github-actions-docker-node-raw
  • /wizard-ci error-tracking-upload-source-maps/cicd-github-actions-nested-docker-node-raw
  • /wizard-ci error-tracking-upload-source-maps/cicd-github-actions-node-raw
  • /wizard-ci error-tracking-upload-source-maps/cicd-gitlab-node-raw
  • /wizard-ci error-tracking-upload-source-maps/cicd-ssh-vps-node-raw
  • /wizard-ci error-tracking-upload-source-maps/flutter
  • /wizard-ci error-tracking-upload-source-maps/ios
  • /wizard-ci error-tracking-upload-source-maps/next
  • /wizard-ci error-tracking-upload-source-maps/next-no-posthog
  • /wizard-ci error-tracking-upload-source-maps/node-raw
  • /wizard-ci error-tracking-upload-source-maps/node-rollup
  • /wizard-ci error-tracking-upload-source-maps/node-rollup-typescript-plugin
  • /wizard-ci error-tracking-upload-source-maps/node-webpack
  • /wizard-ci error-tracking-upload-source-maps/nuxt-3-6
  • /wizard-ci error-tracking-upload-source-maps/nuxt-4-3
  • /wizard-ci error-tracking-upload-source-maps/react-native
  • /wizard-ci error-tracking-upload-source-maps/react-vite
  • /wizard-ci error-tracking-upload-source-maps/rust
  • /wizard-ci misc/quack-quack
  • /wizard-ci revenue/stripe

Results will be posted here when complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant