Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
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.
Install Checking Deploy Timing
$ npx skills add PostHog/posthog --skill checking-deploy-timing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog checking-deploy-timing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/posthog_ai/skills/checking-deploy-timing .claude/skills/checking-deploy-timing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "checking-deploy-timing" agent skill from https://github.com/PostHog/posthog/tree/master/products/posthog_ai/skills/checking-deploy-timing into .claude/skills/checking-deploy-timing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-deploy-timing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog/tree/master/products/posthog_ai/skills/checking-deploy-timingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog --skill checking-deploy-timing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog checking-deploy-timing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/posthog_ai/skills/checking-deploy-timing .agents/skills/checking-deploy-timing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "checking-deploy-timing" agent skill from https://github.com/PostHog/posthog/tree/master/products/posthog_ai/skills/checking-deploy-timing into .agents/skills/checking-deploy-timing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-deploy-timing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill checking-deploy-timing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog checking-deploy-timing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/posthog_ai/skills/checking-deploy-timing .cursor/skills/checking-deploy-timing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "checking-deploy-timing" agent skill from https://github.com/PostHog/posthog/tree/master/products/posthog_ai/skills/checking-deploy-timing into .cursor/skills/checking-deploy-timing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-deploy-timing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog.git --path products/posthog_ai/skills/checking-deploy-timing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog --skill checking-deploy-timing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog checking-deploy-timing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/posthog_ai/skills/checking-deploy-timing .gemini/skills/checking-deploy-timing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "checking-deploy-timing" agent skill from https://github.com/PostHog/posthog/tree/master/products/posthog_ai/skills/checking-deploy-timing into .gemini/skills/checking-deploy-timing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-deploy-timing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog checking-deploy-timingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog --skill checking-deploy-timing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/posthog_ai/skills/checking-deploy-timing .github/skills/checking-deploy-timing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "checking-deploy-timing" agent skill from https://github.com/PostHog/posthog/tree/master/products/posthog_ai/skills/checking-deploy-timing into .github/skills/checking-deploy-timing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-deploy-timing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog --skill checking-deploy-timing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog checking-deploy-timing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/posthog_ai/skills/checking-deploy-timing .opencode/skills/checking-deploy-timing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "checking-deploy-timing" agent skill from https://github.com/PostHog/posthog/tree/master/products/posthog_ai/skills/checking-deploy-timing into .opencode/skills/checking-deploy-timing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "checking-deploy-timing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
checking-deploy-timing- GitHub stars
- 40k
- Token cost
- ~923 tokens
- SKILL.md length
- 429 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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.
- Works in 4 steps: Find the change's merge commit. Identify… → List the target environment's deploys… → Confirm the deployed commit actually… → …
- PostHog staff ask when was X deployed
- SKILL.md covers The deploy annotations, Workflow and Notes
- Calls gh
What it does
Checking Deploy Timing is an agent skill from PostHog/posthog, published by the product's own GitHub organization. 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…
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with PostHog, Git and GitHub. The repository describes itself as: :hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error…
When your agent uses it
- 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
Example prompts
- “when was X deployed”
- “is my change live in the US/EU yet”
- “has my PR shipped”
- “/checking-deploy-timing”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Find the change's merge commit. Identify the PR (e.g. gh search prs --repo PostHog/posthog --author ""), then gh pr view --repo…
- List the target environment's deploys around the merge, oldest-first. Match the region the user asked about (prod-us for "the US", prod-eu…
- Confirm the deployed commit actually contains the merge commit. A later date_marker is necessary but not sufficient — a deploy can fire…
- Report the deploy time (and PR/commit) for the region asked about. Mention other regions if relevant — prod-us and prod-eu usually deploy…
What it can do on your machine
Read from SKILL.md and the folder at commit 10f9ad7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Checking Deploy Timing loads about 923 tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 429 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 429 words (~923 tokens).
“PostHog's CI writes a deploy marker into the project as an annotation every time a commit ships to an environment. These annotations are hidden_in_user_interface: true, so they don't show in the UI and are easy to forget — but they…”
- name
- checking-deploy-timing
Files
Just SKILL.md in products/posthog_ai/skills/checking-deploy-timing of PostHog/posthog.
Open the folder on GitHubat commit 10f9ad7
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in PostHog/posthog, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Checking Deploy Timing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Checking Deploy Timing this skillPostHog/posthog | 40k | — | ~923 | Automated safety check: Pass | Custom licence | |
| Contributor-First PR MergeHKUDS/OpenHarness | 16k | 1 repos | ~847 | Automated safety check: Pass | MIT | |
| Create Pull Requestcline/cline | 70k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Pull Request Title and Body Writeropeninterpreter/openinterpreter | 69k | 2 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
- Official
PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
More from PostHog/posthog
All 252 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Categories
Questions about Checking Deploy Timing
What does Checking Deploy Timing do?
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. Checking Deploy Timing is an agent skill from PostHog/posthog, published by the product's own GitHub organization. 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.
When should I use Checking Deploy Timing?
Checking Deploy Timing fits situations like: 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.
How do I install Checking Deploy Timing in Claude Code?
Run `npx skills add PostHog/posthog --skill checking-deploy-timing -a claude-code`. Or copy the skill folder (products/posthog_ai/skills/checking-deploy-timing in PostHog/posthog) into .claude/skills/checking-deploy-timing in your project. Claude Code loads it when a task matches its description.
How do I install Checking Deploy Timing in Codex?
Run `npx skills add PostHog/posthog --skill checking-deploy-timing -a codex`. Or copy the skill folder (products/posthog_ai/skills/checking-deploy-timing in PostHog/posthog) into .agents/skills/checking-deploy-timing in your project. Codex loads it when a task matches its description.
Can I use Checking Deploy Timing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog --skill checking-deploy-timing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/checking-deploy-timing, .gemini/skills/checking-deploy-timing, .github/skills/checking-deploy-timing and .opencode/skills/checking-deploy-timing in your project.
What does Checking Deploy Timing need to run?
Going by SKILL.md and its folder, Checking Deploy Timing needs the command-line tools its instructions call (gh).
Does Checking Deploy Timing access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Checking Deploy Timing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Checking Deploy Timing use?
Checking Deploy Timing has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Checking Deploy Timing use?
About 923 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Checking Deploy Timing?
Skills that share tags, products or a category with Checking Deploy Timing: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Checking Deploy Timing?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,182 GitHub stars. The repository holds 252 skills in this directory. The repository was last updated on October 8, 2026.
Source: PostHog/posthog on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.