posthog-ship-fix

Draft PR-ready fixes for PostHog documentation or code gaps from triage reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-ship-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: posthog-ship-fix
Source: https://github.com/mongo-ai/posthog-triage-agent/tree/main/.claude/skills/posthog-ship-fix
Command: npx skills add https://github.com/mongo-ai/posthog-triage-agent --skill posthog-ship-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Support engineers must manually locate the correct PostHog file, draft the necessary change, and create a PR after a triage report highlights a docs gap or simple fix. This skill automates that workflow, turning the insight into a ready‑to‑submit PR brief.

Core Features & Use Cases

  • File discovery: Maps product areas to repository paths and retrieves the current file content.
  • Change drafting: Generates doc or code edits that follow PostHog’s style guidelines.
  • PR brief generation: Produces a complete markdown brief with context, verification steps, and source ticket reference.
  • Use case: After a triage report flags a missing troubleshooting step, the skill creates the exact markdown snippet and PR brief for the engineer.

Quick Start

Ask the skill to create a PR brief for a documentation gap identified in the latest triage report.

Frequently Asked Questions about posthog-ship-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert triage findings into a PR-ready documentation fix?

How to draft a PR brief from a support triage report: locate the exact file using repository paths, generate the markdown snippet, and format the brief with context and source ticket references for engineers.

Can I automate documentation gap fixes in PostHog repositories?

Yes, you can automate documentation gap fixes in PostHog repositories by retrieving current file content via the GitHub API, generating compliant markdown edits, and outputting a ready-to-submit PR brief.

What is included in an automated PR brief for a code or docs gap?

An automated PR brief for a code or docs gap includes the exact markdown-formatted change, contextual details, verification steps, and the source triage ticket reference for engineer review.

Does this triage automation require access to GitHub API and repository paths?

Yes, this triage automation requires GitHub API access and repository paths to retrieve current file content, locate the exact file needing edits, and format the final PR brief.

Why does my support triage workflow need a PR brief generator?

A PR brief generator streamlines your support triage workflow by eliminating the manual process of locating files and drafting changes, instantly turning identified gaps into ready-to-submit markdown PR content.