# checking-deploy-timing

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 200 installs · ★ 101 repo stars
- Author: PostHog
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/PostHog/ai-plugin/tree/HEAD/skills/checking-deploy-timing/SKILL.md
- Updated: 2026-10-24
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/checking-deploy-timing

## What it 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.

## Requirements
- Works with: GitHub

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/checking-deploy-timing/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/checking-deploy-timing/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/checking-deploy-timing/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/checking-deploy-timing/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install PostHog/ai-plugin skills/checking-deploy-timing
```

2. **Manually: put the files in place**
- File: `.github/skills/checking-deploy-timing/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/PostHog/ai-plugin --path skills/checking-deploy-timing
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/checking-deploy-timing/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add PostHog/ai-plugin --skill checking-deploy-timing -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/PostHog/ai-plugin/tree/HEAD/skills/checking-deploy-timing/SKILL.md

## When to use it
- 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
- 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>`.

## Similar
- [deploy](https://affpapa.org/en/nevibecode/commands/deploy.md) — command · ★ 3232 repo stars
- [gh-switch](https://affpapa.org/en/nevibecode/skills/sentimony-gh-switch.md) — skill · 2200 installs
- [publish-project-to-github](https://affpapa.org/en/nevibecode/skills/publish-project-to-github.md) — skill · 1500 installs
- [github-cli](https://affpapa.org/en/nevibecode/skills/github-cli.md) — skill · 128 installs
- [create-pull-request](https://affpapa.org/en/nevibecode/commands/create-pull-request.md) — command · 411 installs
- [create-pr](https://affpapa.org/en/nevibecode/skills/create-pr.md) — skill · 1200 installs

From the same set: [posthog/ai-plugin](https://affpapa.org/en/nevibecode/by/posthog/ai-plugin.md) — 82 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
