review-hog-authoring — Claude Code skill: what it does, how to install
review-hog-authoring — a guide skill for writing custom PostHog Review pieces: extra PR perspectives, your own blind-spot sweep, and the bars that decide what gets published or fixed.
no license 187 installs ★ 101 updated 2026-10-24
npx skills add PostHog/ai-plugin --skill review-hog-authoring -a claude-codeWhat review-hog-authoring does
PostHog Review checks pull requests on its own, and this skill is the manual for handing it extra reviewers. A run splits the PR into chunks, applies every enabled perspective to each chunk, sweeps for blind spots once, then keeps only findings that clear the validation bar. After publishing, the resolution stage works through open threads and commits changes that are both worth making and safe.
The skill walks the agent through the job: list the team's review-hog-* skills, read the canonical for the kind being written, settle the direction with the user, then create the LLMSkill row with posthog:skill-create rather than handing over text to paste. Names follow a fixed prefix per kind, such as review-hog-perspective-<slug> or review-hog-validation-<slug>, and that prefix is what the Code review tab and review runs look for. Later edits go through posthog:skill-update; duplicating a canonical with skill-duplicate drags seeded metadata along.
None of this lands without the PostHog MCP skill tools available to the agent. A newly written skill also starts switched off for its author: perspectives get toggled in Inbox → Code review → Perspectives, while a blind-spot, validation or resolution pick replaces whichever one is currently active. Versions are pinned when a run begins, so an edit mid-review shows up next time.
What it helps with
- add a specialist lens to automated PR reviews
- tighten which findings get published on a pull request
- set your own bar for which review comments get implemented
- swap the final blind-spot sweep for one aimed at a known weak spot
- create a team
LLMSkillfrom the agent instead of by hand
Example prompts for the agent
- Create a custom review perspective for database migrations and call it
review-hog-perspective-migrations. - Show me the canonical blind-spot skill, then author our own sweep for the area we keep missing.
- Tune the validation criteria so only production-breaking findings reach the PR.
How to install review-hog-authoring
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill review-hog-authoring -a claude-code2Manually: put the files in place
~/.claude/skills/review-hog-authoring/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-hog-authoring/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill review-hog-authoring -a codex2Manually: put the files in place
.agents/skills/review-hog-authoring/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill review-hog-authoring -a cursor2Manually: put the files in place
.cursor/skills/review-hog-authoring/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/review-hog-authoring2Manually: put the files in place
.github/skills/review-hog-authoring/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill review-hog-authoring -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/review-hog-authoringManually: put the files in place
.devin/skills/review-hog-authoring/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill review-hog-authoring -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-hog-authoring
How do I install review-hog-authoring in Claude Code?
Run npx skills add PostHog/ai-plugin --skill review-hog-authoring -a claude-code. The skill lands at ~/.claude/skills/review-hog-authoring/SKILL.md.
What does review-hog-authoring do?
It guides the agent through authoring custom perspectives, blind-spot checks, validation criteria and resolution criteria for PostHog Review, then through creating the team skill and switching it on.
Why is my new perspective not running?
Custom skills start inactive. Enable the perspective in Inbox → Code review → Perspectives; for blind-spot, validation or resolution only one is active at a time, and a skill's version is pinned when a run starts.