checking-deploy-timing

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...

Publisher type
Official
Repository
posthog/skills
Skill
checking-deploy-timing
GitHub repository stars
61
npx skills add https://github.com/posthog/skills --skill checking-deploy-timing

Agent skills can contain instructions that call tools or modify files. Review the source and permissions before installation.

What this resource does

checking-deploy-timing is a reusable AI-agent instruction package published by PostHog. It gives a compatible agent a repeatable procedure for work in this area: Product analytics.

Best for

  • Founders and teams using an AI coding or work agent for tasks in this area: Product analytics.
  • Repeatable work that matches this capability: 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...
  • Users who want a publisher-defined workflow they can inspect before running.

What to prepare

  • A compatible AI agent that supports Agent Skills.
  • Access to the project or files the task will use.
  • Any provider accounts, command-line tools, or credentials requested by the skill.
  • A safe branch or backup when the skill may modify files.

How to use it

  1. Open the original repository and review SKILL.md, referenced files, scripts, and requested permissions.
  2. Copy the install command and run it from the workspace where you want to use checking-deploy-timing.
  3. Reload or restart the agent if it does not discover the new skill immediately.
  4. Give the agent a concrete task in this area: Product analytics. Explicitly name checking-deploy-timing when you want to require its use.
  5. Review the proposed actions and output before approving file changes, shell commands, credentials, or external writes.

Example request

Use the checking-deploy-timing skill for this task. First inspect the available context, explain the proposed approach, and wait for approval before any sensitive or destructive action.

Before you continue: Publisher category: Official. Publication in this catalog is not a security guarantee. Review the current repository before installation.

Source and review

Source check: 2026-09-05.

PostHog