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
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a claude-codeWhat 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 inprod-euyet, or still only ondev? - Verify the
prod-usdeploy 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-code2Manually: put the files in place
~/.claude/skills/checking-deploy-timing/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/checking-deploy-timing/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a codex2Manually: put the files in place
.agents/skills/checking-deploy-timing/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a cursor2Manually: put the files in place
.cursor/skills/checking-deploy-timing/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/checking-deploy-timing2Manually: put the files in place
.github/skills/checking-deploy-timing/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/checking-deploy-timingManually: put the files in place
.devin/skills/checking-deploy-timing/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.