Skip to content

Trim CLAUDE.md into skills and drop posthog-remote MCP - #140

Merged
haacked merged 1 commit into
mainfrom
haacked/checkup
Jul 13, 2026
Merged

Trim CLAUDE.md into skills and drop posthog-remote MCP#140
haacked merged 1 commit into
mainfrom
haacked/checkup

Conversation

@haacked

@haacked haacked commented Jul 13, 2026

Copy link
Copy Markdown
Owner

Move the GitHub PR operations reference and PostHog specific workflow, database access, production architecture, and SDK repo notes out of the always loaded CLAUDE.md into two new skills, github-pr-operations and posthog-context. Safety critical rules (never post PR comments without approval, never use posthog-db against prod, never use socket IP addresses) stay in CLAUDE.md as standing one liners.

Remove the decommissioned posthog-remote MCP server from install.sh.

Update investigator.md to query PostHog product data via posthog-cli over Bash instead of the removed mcp__posthog-remote__exec tool.

Test plan

  • Ran sh -n ai/install.sh to confirm it still parses.
  • Grepped the repo for posthog-remote to confirm no dangling references remain.
  • Read the trimmed CLAUDE.md and the new skill files end to end to confirm nothing safety critical was silently dropped in the move.

Move the GitHub PR operations reference and PostHog-specific workflow,
database access, production architecture, and SDK repo notes out of the
always-loaded CLAUDE.md into two new skills: github-pr-operations and
posthog-context. Safety-critical rules (never post PR comments without
approval, never use posthog-db against prod, never use socket IP
addresses) stay in CLAUDE.md as standing one-liners.

Remove the decommissioned posthog-remote MCP server from install.sh and
update investigator.md to query PostHog product data via posthog-cli
over Bash instead of the mcp__posthog-remote__exec tool.
@haacked
haacked marked this pull request as ready for review July 13, 2026 19:20
@haacked
haacked requested a review from Copilot July 13, 2026 19:20
@haacked
haacked merged commit 19eb06d into main Jul 13, 2026
1 check passed
@haacked
haacked deleted the haacked/checkup branch July 13, 2026 19:21

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refactors always-loaded AI guidance by extracting PostHog- and GitHub-PR-specific operational references into dedicated skills, removes the decommissioned posthog-remote MCP server from installation, and updates the investigator agent guidance to use posthog-cli for product-data queries.

Changes:

  • Add two new skills: posthog-context and github-pr-operations, moving repo-specific workflows/mechanics out of ai/CLAUDE.md.
  • Remove the posthog-remote MCP server from ai/install.sh.
  • Update ai/agents/investigator.md to replace the removed mcp__posthog-remote__exec guidance with posthog-cli api via restricted Bash.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.

Show a summary per file
File Description
ai/skills/posthog-context/SKILL.md New PostHog-specific context skill (workflow, DB rules, architecture notes, SDK repo locations).
ai/skills/github-pr-operations/SKILL.md New skill documenting PR comment/reply mechanics and thread resolution via gh.
ai/install.sh Drops posthog-remote from the MCP server installation list and related env handling.
ai/CLAUDE.md Trims always-loaded content down to safety-critical one-liners and pointers to the new skills.
ai/agents/investigator.md Switches product-data guidance from removed MCP tool to posthog-cli api via restricted Bash.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread ai/agents/investigator.md
3. Note which approach you used in the Assumptions field.
2. **Pick the region.** PostHog runs in US and EU. If the hypothesis doesn't specify, check the context or default to US (`mcp__grafana__*`); note which you used.
3. **Execute queries.** Use Grafana MCP tools (`mcp__grafana__*` or `mcp__grafana-eu__*`) for metrics and logs, `mcp__posthog-db__*` for database state. Do not copy large query outputs into your report — extract the key numbers.
3. **Execute queries.** Use Grafana MCP tools (`mcp__grafana__*` or `mcp__grafana-eu__*`) for metrics and logs, `mcp__posthog-db__*` for database state, `posthog-cli api` (via Bash) for PostHog product data. Do not copy large query outputs into your report — extract the key numbers.
Comment thread ai/agents/investigator.md
@@ -49,9 +49,9 @@ You have access to:
- `mcp__grafana__*` — US Grafana (metrics, logs, dashboards, Loki, Prometheus)
- `mcp__grafana-eu__*` — EU Grafana (same capabilities, EU region)
- `mcp__posthog-db__*` — PostHog production database (for tenant state, schema inspection)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants