Skip to main content
skill CX Codex

checking-deploy-timing — Claude Code skill: when did my change ship

checking-deploy-timing tells you when a commit or PR reached prod-us or prod-eu by reading PostHog's hidden deploy annotations and matching them against the merge commit on GitHub.

no license 200 installs ★ 101 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a claude-code
Open on GitHub

What checking-deploy-timing does

Every time a commit reaches an environment, PostHog's CI writes a deploy annotation into the project. The markers stay out of the UI, so they get overlooked, yet they hold the real ship time. The skill pulls them with posthog:annotations-list and the search deploy, then reads content (for example Deployed PostHog/posthog@<sha> to <env>), creation_type GIT and date_marker in UTC.

The merge commit comes first: find the PR with gh search prs --repo PostHog/posthog, then read mergedAt and mergeCommit via gh pr view. Annotations arrive newest-first, so the agent pages back with offset until it reaches the merge window and walks forward from there. A timestamp after the merge is not proof on its own, since a deploy may fire right after and still carry an older commit. Ancestry gets checked with gh api repos/PostHog/posthog/compare/<merge_sha>...<deployed_sha>; behind_by: 0 means the change is in.

Regions map to prod-us and prod-eu, while dev is internal staging. You need the gh CLI and access to PostHog annotations, and the whole flow is tied to PostHog/posthog — another repo leaves it nothing to correlate.

What it helps with

  • check whether a commit already reached prod-us
  • find the merge commit behind a shipped PR
  • separate a code change from a jump in event volume
  • confirm the deployed build actually carries the merge
  • compare ship times for the US and EU regions

Example prompts for the agent

  • My cache-fix PR just merged — which region has it now? Check the deploy annotations.
  • Is commit <sha> live in prod-eu yet, or still only on dev?
  • Verify the prod-us deploy includes merge commit <merge_sha>.

How to install checking-deploy-timing

1Skills CLI (Vercel)

npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a claude-code

2Manually: put the files in place

~/.claude/skills/checking-deploy-timing/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/checking-deploy-timing/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about checking-deploy-timing

How do I install checking-deploy-timing in Claude Code?

Run npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a claude-code. The skill lands at ~/.claude/skills/checking-deploy-timing/SKILL.md.

What does checking-deploy-timing do?

It dates the release of a commit or PR in a given region: it lists the hidden GIT deploy annotations, ties them to the merge commit on GitHub, and confirms the built commit contains the change.

What does it need to run?

The gh CLI for the PR and compare calls, plus access to PostHog's annotation list through posthog:annotations-list, which is where deploy markers live.

Similar skills

All skills for Git and GitHub →

From the same set82

The whole set →
exploring-mcp-intent-clusters exploring-mcp-intent-clusters analyzes PostHog MCP agent intent clusters to reveal what agents attempt to do, tool failure patterns, and semantic routing competition. CX Codex +1 202installs managing-reminders managing-reminders is a Claude Code skill that creates and manages private PostHog reminders with one-time or repeating schedules. It can nudge you about a task or resource. CX Codex +1 202installs signals-scout-apm signals-scout-apm watches OpenTelemetry traces in PostHog for error-rate and latency shifts per service, new error signatures and traffic drops, and files a report only on a confirmed change. CX Codex +1 202installs exploring-mcp-tool-usage exploring-mcp-tool-usage — a routing skill for PostHog MCP analytics: it offers a menu of questions about tool calls, then hands you to the query that answers it. CX Codex +1 200installs setting-up-a-custom-rest-source setting-up-a-custom-rest-source — a skill for Claude Code and Codex that links arbitrary REST APIs to the PostHog data warehouse using a JSON manifest. Activates when importing custom endpoints without native connectors. CX Codex +1 199installs exploring-ai-failures exploring-ai-failures reads real production traces from PostHog and returns a ranked list of the ways your LLM feature breaks. CX Codex +1 198installs resolving-ingestion-warnings resolving-ingestion-warnings walks through PostHog ingestion warnings: dropped events, rejected person merges, oversized payloads. Use it when event counts look low or identify calls misbehave. CX Codex +1 197installs exploring-scouts exploring-scouts reads the state of PostHog Signals scouts: which ones a project has, how recent runs went, and where their reports ended up. Read-only. CX Codex +1 197installs

Project sponsors

Companies that keep this analytics open