Release Flow
romankurnovskii/BrewMate
Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update…
A skill your agent uses when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a…
Install Gating Production Deploys
$ npx skills add PostHog/posthog --skill gating-production-deploys -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog gating-production-deploys --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/.agents/skills/gating-production-deploys .claude/skills/gating-production-deploys && 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 "gating-production-deploys" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/gating-production-deploys into .claude/skills/gating-production-deploys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gating-production-deploys", 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/.agents/skills/gating-production-deploysType 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 gating-production-deploys -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog gating-production-deploys --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/.agents/skills/gating-production-deploys .agents/skills/gating-production-deploys && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "gating-production-deploys" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/gating-production-deploys into .agents/skills/gating-production-deploys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gating-production-deploys", 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 gating-production-deploys -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog gating-production-deploys --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/.agents/skills/gating-production-deploys .cursor/skills/gating-production-deploys && 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 "gating-production-deploys" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/gating-production-deploys into .cursor/skills/gating-production-deploys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gating-production-deploys", 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 .agents/skills/gating-production-deploys--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 gating-production-deploys -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog gating-production-deploys --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/.agents/skills/gating-production-deploys .gemini/skills/gating-production-deploys && 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 "gating-production-deploys" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/gating-production-deploys into .gemini/skills/gating-production-deploys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gating-production-deploys", 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 gating-production-deploysInstalls 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 gating-production-deploys -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/.agents/skills/gating-production-deploys .github/skills/gating-production-deploys && 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 "gating-production-deploys" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/gating-production-deploys into .github/skills/gating-production-deploys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gating-production-deploys", 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 gating-production-deploys -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 gating-production-deploys --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/.agents/skills/gating-production-deploys .opencode/skills/gating-production-deploys && 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 "gating-production-deploys" agent skill from https://github.com/PostHog/posthog/tree/master/.agents/skills/gating-production-deploys into .opencode/skills/gating-production-deploys/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gating-production-deploys", 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
gating-production-deploys- GitHub stars
- 40k
- Token cost
- ~751 tokens
- SKILL.md length
- 155 words
- Files
- 1
- Skills in repo
- 252
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a…
- Editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action)
- SKILL.md covers The gate and Patterns
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Dispatches a production deploy (a commitstateupdate repositorydispatch to PostHog/charts)
What it does
Gating Production Deploys is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Use when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a commitstateupdate repositorydispatch to PostHog/charts). Those run from a single canonical deploy repo, gated by the CDDEPLOYENABLED variable. Does NOT apply to workflows that publish GitHub releases, npm, crates, or Homebrew — those stay on the public repo.
Its SKILL.md is about 750 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 DevOps & Cloud, covering Containers and CI/CD. It works with PostHog, Docker, GitHub and Homebrew. 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
- Editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action)
- Dispatches a production deploy (a commitstateupdate repositorydispatch to PostHog/charts)
Example prompts
- “/gating-production-deploys”
Requirements
- Docker
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
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Gating Production Deploys loads about 751 tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 155 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 155 words (~751 tokens).
“Container-image pushes and Charts deploy dispatches run from one canonical deploy repo, selected by the CD_DEPLOY_ENABLED variable. Gate every such step or it publishes/deploys from the wrong place.”
- name
- gating-production-deploys
Files
Just SKILL.md in .agents/skills/gating-production-deploys 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
Gating Production Deploys 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 |
|---|---|---|---|---|---|---|
| Gating Production Deploys this skillPostHog/posthog | 40k | — | ~751 | Automated safety check: Pass | Custom licence | |
| Release Flowromankurnovskii/BrewMate | 301 | — | ~976 | Automated safety check: Pass | MIT | |
| Data Processingaiskillstore/marketplace | 430 | 1 repos | ~720 | Automated safety check: Notes | MIT | |
| Releasing MarchatCod-e-Codes/marchat | 137 | — | ~801 | Automated safety check: Pass | MIT | |
| Actmajiayu000/claude-skill-registry | 666 | 1 repos | ~1.4k | Automated safety check: Notes | Apache-2.0 | |
| Configuration GeneratorArabelaTso/Skills-4-SE | 253 | — | ~2.8k | Automated safety check: Notes | Apache-2.0 |
Similar skills
Data Processing
aiskillstore/marketplace
Process JSON with jq and YAML/TOML with yq. An agent skill from aiskillstore/marketplace.
Releasing Marchat
Cod-e-Codes/marchat
Prepares marchat releases: version bumps, CHANGELOG, packaging checksums, GitHub Actions release workflow, and Docker tags.
Act
majiayu000/claude-skill-registry
Runs GitHub Actions workflows on your own machine in Docker containers with act, so CI can be tested without pushing.
Configuration Generator
ArabelaTso/Skills-4-SE
Generate configuration files for applications, services, and infrastructure.
Project References
aiskillstore/marketplace
Look up conventions, patterns, and concrete implementations from your own GitHub repositories checked out locally under ~/projects/referenzen/.
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 Gating Production Deploys
What does Gating Production Deploys do?
A skill your agent uses when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a…. Gating Production Deploys is an agent skill from PostHog/posthog, published by the product's own GitHub organization. Use when adding or editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action) or dispatches a production deploy (a commitstateupdate repositorydispatch to PostHog/charts).
When should I use Gating Production Deploys?
Gating Production Deploys fits situations like: editing a GitHub Actions workflow that pushes a container image to a registry (ECR/ghcr/Docker Hub via build-push-action); dispatches a production deploy (a commitstateupdate repositorydispatch to PostHog/charts).
How do I install Gating Production Deploys in Claude Code?
Run `npx skills add PostHog/posthog --skill gating-production-deploys -a claude-code`. Or copy the skill folder (.agents/skills/gating-production-deploys in PostHog/posthog) into .claude/skills/gating-production-deploys in your project. Claude Code loads it when a task matches its description.
How do I install Gating Production Deploys in Codex?
Run `npx skills add PostHog/posthog --skill gating-production-deploys -a codex`. Or copy the skill folder (.agents/skills/gating-production-deploys in PostHog/posthog) into .agents/skills/gating-production-deploys in your project. Codex loads it when a task matches its description.
Can I use Gating Production Deploys 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 gating-production-deploys -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gating-production-deploys, .gemini/skills/gating-production-deploys, .github/skills/gating-production-deploys and .opencode/skills/gating-production-deploys in your project.
What does Gating Production Deploys need to run?
SKILL.md names no scripts, command-line tools or credentials: Gating Production Deploys is instructions for the agent only. Our summary lists: Docker.
Does Gating Production Deploys access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Gating Production Deploys 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 Gating Production Deploys use?
Gating Production Deploys 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 Gating Production Deploys use?
About 751 tokens (SKILL.md is roughly 3k 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 Gating Production Deploys?
Skills that share tags, products or a category with Gating Production Deploys: Release Flow (romankurnovskii/BrewMate, 301 stars), Data Processing (aiskillstore/marketplace, 430 stars), Releasing Marchat (Cod-e-Codes/marchat, 137 stars) and Act (majiayu000/claude-skill-registry, 666 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Gating Production Deploys?
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.