checking-deploy-timing
Skill96 starsChanged 37 days agoNo licenceView on GitHub
Determine when a PostHog code change reached a given environment by reading the hidden GIT deploy annotations in the project and correlating them with the merge commit on GitHub. Use when PostHog staff ask "when was X deployed", "is my change live in the US/EU yet", "has my PR shipped", "did the fix roll out to prod-us", or otherwise want to know whether/when a commit, PR, or feature went out to a region. Do not answer deploy-timing questions from event/data volume alone — that only shows when data changed, not when code shipped.
Other versions1 project uses a version of this.
Word for word · 1
- PostHog/skills★ 76100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository179 other files it gives its agents.
- adding-warehouse-person-propertiesSkill
- analyzing-ai-citationsSkill
- analyzing-expensive-usersSkill
- analyzing-experiment-session-replaysSkill
- analyzing-funnel-correlationSkill
- analyzing-offline-evaluationsSkill
- analyzing-task-runsSkill
- assessing-heatmapsSkill
- auditing-endpointsSkill
- auditing-experiments-flagsSkill
- auditing-warehouse-source-healthSkill
- auditing-warehouse-view-healthSkill
- authoring-data-quality-checksSkill
- authoring-error-tracking-alertsSkill
- authoring-log-alertsSkill
- authoring-scoutsSkill
- building-a-dashboardSkill
- building-canvasesSkill
- building-html-canvasesSkill
- building-loopsSkill
- building-react-quill-canvasesSkill
- building-workflowsSkill
- checking-member-accessSkill
- choosing-trend-or-slope-viewSkill
- cleaning-up-stale-feature-flagsSkill
- composing-grid-canvasesSkill
- configuring-experiment-analyticsSkill
- configuring-experiment-rolloutSkill
- consuming-endpoints-from-client-codeSkill
- context-layer-consolidationSkill
- context-layer-dreamingSkill
- context-layer-health-checkSkill
- copying-endpoints-across-projectsSkill
- copying-flags-across-projectsSkill
- creating-ai-subscriptionSkill
- creating-an-endpointSkill
- creating-box-plot-insightsSkill
- creating-experimentsSkill
- creating-online-evaluationsSkill
- creating-replay-vision-scannersSkill
- creating-surveysSkill
- debugging-experimentsSkill
- debugging-failed-data-quality-checksSkill
- debugging-surveysSkill
- designing-email-templatesSkill
- designing-replay-vision-scannersSkill
- diagnosing-ci-and-merge-bottlenecksSkill
- diagnosing-endpoint-performanceSkill
- diagnosing-experiment-healthSkill
- diagnosing-failed-warehouse-syncsSkill
- diagnosing-missing-recordingsSkill
- diagnosing-sdk-healthSkill
- diagnosing-stacktrace-symbolicationSkill
- downloading-batch-export-filesSkill
- exploring-ai-failuresSkill
- exploring-apm-tracesSkill
- exploring-autocapture-eventsSkill
- exploring-endpoint-execution-logsSkill
- exploring-live-trafficSkill
- exploring-llm-clustersSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.