Official agent skill

Review Hog Authoring

by PostHog in PostHog/posthog

How to author custom PostHog Review skills: the review perspectives, blind-spot checks, validation criteria, and resolution criteria that drive PostHog Review's automated PR reviews.

OfficialCustom licenceAuto-check passedDevelopment

Install Review Hog Authoring

skills CLI
$ npx skills add PostHog/posthog --skill review-hog-authoring -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install PostHog/posthog review-hog-authoring --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/PostHog/posthog.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/review_hog/skills/review-hog-authoring .claude/skills/review-hog-authoring && rm -rf skills-src

Use ~/.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/

Facts

Skill name
review-hog-authoring
GitHub stars
40k
Token cost
~2k tokens
SKILL.md length
1,020 words
Files
1
Skills in repo
254
Repo updated
First seen
Licence
Custom licence

At a glance

How to author custom PostHog Review skills: the review perspectives, blind-spot checks, validation criteria, and resolution criteria that drive PostHog Review's automated PR reviews.

  • Works in 5 steps: Ground yourself. Using the PostHog MCP… → Interview the user. Ask what the skill… → Draft the body following the per-kind… → …
  • A user wants a new review perspective (a specialist lens on their PRs)
  • SKILL.md covers Authoring flow, Writing a review perspective, Writing a blind-spot check and Writing validation criteria, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Review Hog Authoring is an agent skill from PostHog/posthog, published by the product's own GitHub organization. How to author custom PostHog Review skills: the review perspectives, blind-spot checks, validation criteria, and resolution criteria that drive PostHog Review's automated PR reviews. Use when a user wants a new review perspective (a specialist lens on their PRs), a custom blind-spot sweep, their own validation bar for which findings get published, or their own bar for which review comments get implemented. Trigger on "create a PostHog Review perspective", "custom review perspective", "my own blind-spot check"…

Its SKILL.md is about 2k 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, covering Pull requests. It works with PostHog. 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

  • A user wants a new review perspective (a specialist lens on their PRs)
  • A custom blind-spot sweep
  • Their own validation bar for which findings get published
  • Their own bar for which review comments get implemented

Example prompts

  • “create a PostHog Review perspective”
  • “custom review perspective”
  • “my own blind-spot check”
  • “/review-hog-authoring”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Ground yourself. Using the PostHog MCP skill tools, skill-list the team's review-hog-*
  2. Interview the user. Ask what the skill should focus on, and offer a few concrete directions
  3. Draft the body following the per-kind guidance below. Keep it a focused instruction set the
  4. Create the skill yourself with posthog:skill-create — actually create the team LLMSkill
  5. Tell the user how to activate it. A custom skill starts inactive for them

What it can do on your machine

Read from SKILL.md and the folder at commit c012c8d. 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.

    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

Review Hog Authoring loads about 2k tokens when it runs. Until then it costs about 168 tokens; SKILL.md has 1,020 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~168
When it runs · the whole SKILL.md, loaded when a task matches
~2k

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 1,020 words (~2,031 tokens).

“PostHog Review is PostHog's automated PR reviewer. A review splits the PR into chunks, then for each chunk runs every enabled perspective in parallel (independent specialist lenses), a single blind-spot check afterwards (a final sweep conditioned on what the perspectives…”

— opening of SKILL.md by PostHog, Custom licence
name
review-hog-authoring
metadata.owner_team
review_hog
metadata.skill_type
authoring

Read the full SKILL.md on GitHub

Files

Just SKILL.md in products/review_hog/skills/review-hog-authoring of PostHog/posthog.

Open the folder on GitHubat commit c012c8d

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

Review Hog Authoring 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.

Review Hog Authoring compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Hog Authoring this skillPostHog/posthog40k—~2kAutomated safety check: PassCustom licence
Create PRUniClipboard/UniClipboard1.9k—~4.6kAutomated safety check: PassAGPL-3.0
Adapter Alignmentevloghq/evlog1.9k—~1.3kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Create PR

    UniClipboard/UniClipboard

    Push the current branch and open a GitHub pull request against main.

    1.9k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Adapter Alignment

    evloghq/evlog

    Twice-monthly check that evlog's drain adapters still send what each provider's own client sends.

    1.9k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • PR Design Doc

    OpenHands/OpenHands

    For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…

    90k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

More from PostHog/posthog

All 254 skills in this repo
  • Authoring Log Alerts

    PostHog/posthog

    Official

    Author useful, low-noise log alerts on services in a PostHog project.

    40k GitHub stars~3k tokensUpdated today
    Auto-check passed
  • Official

    Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…

    40k GitHub stars~4.2k tokensUpdated today
    Auto-check passed
  • Official

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

    40k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Exploring Apm Traces

    PostHog/posthog

    Official

    Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.

    40k GitHub stars~3.5k tokensUpdated today
    Auto-check passed
  • Exploring LLM Traces

    PostHog/posthog

    Official

    Debug and inspect LLM/AI agent traces using PostHog's MCP tools.

    40k GitHub stars~4.4k tokensUpdated today
    Auto-check passed
  • Investigate Metric

    PostHog/posthog

    Official

    Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.

    40k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Review Hog Authoring

What does Review Hog Authoring do?

How to author custom PostHog Review skills: the review perspectives, blind-spot checks, validation criteria, and resolution criteria that drive PostHog Review's automated PR reviews. Review Hog Authoring is an agent skill from PostHog/posthog, published by the product's own GitHub organization. How to author custom PostHog Review skills: the review perspectives, blind-spot checks, validation criteria, and resolution criteria that drive PostHog Review's automated PR reviews.

When should I use Review Hog Authoring?

Review Hog Authoring fits situations like: A user wants a new review perspective (a specialist lens on their PRs); A custom blind-spot sweep; their own validation bar for which findings get published; their own bar for which review comments get implemented.

How do I install Review Hog Authoring in Claude Code?

Run `npx skills add PostHog/posthog --skill review-hog-authoring -a claude-code`. Or copy the skill folder (products/review_hog/skills/review-hog-authoring in PostHog/posthog) into .claude/skills/review-hog-authoring in your project. Claude Code loads it when a task matches its description.

How do I install Review Hog Authoring in Codex?

Run `npx skills add PostHog/posthog --skill review-hog-authoring -a codex`. Or copy the skill folder (products/review_hog/skills/review-hog-authoring in PostHog/posthog) into .agents/skills/review-hog-authoring in your project. Codex loads it when a task matches its description.

Can I use Review Hog Authoring 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 review-hog-authoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-hog-authoring, .gemini/skills/review-hog-authoring, .github/skills/review-hog-authoring and .opencode/skills/review-hog-authoring in your project.

What does Review Hog Authoring need to run?

SKILL.md names no scripts, command-line tools or credentials: Review Hog Authoring is instructions for the agent only.

Does Review Hog Authoring 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 Review Hog Authoring 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 Review Hog Authoring use?

Review Hog Authoring 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 Review Hog Authoring use?

About 2k tokens (SKILL.md is roughly 8.1k 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 Review Hog Authoring?

Skills that share tags, products or a category with Review Hog Authoring: Create PR (UniClipboard/UniClipboard, 1.9k stars), Adapter Alignment (evloghq/evlog, 1.9k stars), Finishing a Development Branch (obra/superpowers, 297k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Hog Authoring?

PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog, which has 40,209 GitHub stars. The repository holds 254 skills in this directory. The repository was last updated on October 10, 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.