signals-scout-pr-follow-up — Claude Code skill: install
signals-scout-pr-follow-up — a Claude Code skill checks merged pull requests against post-deploy telemetry. It looks for the promised effect and regressions tied to a specific change.
no license 122 installs ★ 101 updated 2026-10-24
npx skills add PostHog/ai-plugin --skill signals-scout-pr-follow-up -a claude-codeWhat signals-scout-pr-follow-up does
The skill tracks recently merged pull requests in connected repositories, checks whether each change reached users, then compares project telemetry with the PR’s stated goal. A fix can be checked for a continuing error; a feature change can be checked for signs of use. Assessment starts after deployment, not at merge.
The setup requires the PostHog Signals agent, connected repositories, and access to project analytics. The agent supplies read-only gh access; report and scratchpad tools provide write access for its findings and state. If deployment cannot be established, the skill waits through a soak period, with the duration depending on whether the change is server-side, client-side, or mobile.
What it helps with
- confirm that a merged change reached users
- compare a PR’s intended result with project telemetry
- identify a regression attributable to a particular PR
Example prompts for the agent
- Review recently merged PRs and compare their results with project telemetry.
- Check whether the fix in the merged PR reached users and stopped the error.
- Look for a regression tied to the latest deployed PR.
How to install signals-scout-pr-follow-up
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-pr-follow-up -a claude-code2Manually: put the files in place
~/.claude/skills/signals-scout-pr-follow-up/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/signals-scout-pr-follow-up/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-pr-follow-up -a codex2Manually: put the files in place
.agents/skills/signals-scout-pr-follow-up/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-pr-follow-up -a cursor2Manually: put the files in place
.cursor/skills/signals-scout-pr-follow-up/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/ai-plugin skills/signals-scout-pr-follow-up2Manually: put the files in place
.github/skills/signals-scout-pr-follow-up/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-pr-follow-up -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/ai-plugin --path skills/signals-scout-pr-follow-upManually: put the files in place
.devin/skills/signals-scout-pr-follow-up/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/ai-plugin --skill signals-scout-pr-follow-up -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 signals-scout-pr-follow-up
How do I install signals-scout-pr-follow-up in Claude Code?
Run npx skills add PostHog/ai-plugin --skill signals-scout-pr-follow-up -a claude-code. The skill file is at ~/.claude/skills/signals-scout-pr-follow-up/SKILL.md.
What does signals-scout-pr-follow-up do?
It checks whether merged pull requests have shipped, then compares their intended outcomes with project telemetry. It reports regressions that can be linked to a specific PR.
When does the skill assess a pull request?
It waits until the change is live for users. If the project cannot establish deployment, it uses a waiting period whose length depends on the type of change.