1. Habit
  2. Skills
  3. Diagnosing CI and Merge Bottlenecks skill
PostHog · 2 installs

Diagnosing CI and Merge Bottlenecks skill
Runs by itself, weekly CI health.

CI long pole named weekly.

Install the Diagnosing CI and Merge Bottlenecks skill and make it a habit: follow https://gethabit.dev/skills/posthog/diagnosing-ci-and-merge-bottlenecks.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

2 installs40K starsMIT licenceSource on GitHub ↗

Diagnosing CI and Merge Bottlenecks

by PostHog · 2 installs

The skill

The diagnosing ci and merge bottlenecks skill helps engineering teams use PostHog engineering analytics tools to find slow or flaky workflows, time to merge and stuck pull requests.

Only when you ask.

The habit

CI long pole named weekly.

↻ Runs by itselfweekly CI health

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

weekly CI health. Runs in Claude Code routine.

  • ↻ weekly CI health
  • 0 9 * * 1

02

It checks its work

numbers carry caveats. If a check fails, it tells you.

  • ✓median and p95 are reported side by side
  • ✓bots and drafts are excluded from merge-time stats
  • ✓pending CI is never reported as a settled failure
  • ✓truncated pull-requests results are flagged

03

It remembers

CI health log. The next run reads it first: last week's long pole and p95 values.

loops/ci-bottleneck-weekly-loop/run-log.md

One run, step by step.
Then it stops.

Stop ruleStops after one repo per run.

  1. 01

    Pick the repo

    Call engineering-analytics-sources and pass source_id and repo on.

  2. 02

    Compare windows

    Call workflow-health for two adjacent windows and compare p50 and p95.

  3. 03

    Confirm on PRs

    Use pull-requests to list failing, pending and longest-open PRs.

  4. 04

    Open one PR

    Walk a stuck PR with pr-lifecycle and name the largest gap.

  5. 05

    Report

    Lead with a one-line verdict, then a short table with caveats.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Diagnosing CI and Merge Bottlenecks skill helps.

Use it when

  • ✓ You ask whether CI is getting slower
  • ✓ You find where a PR is stuck
  • ✓ You measure time to merge

Skip it when

  • – You need a verdict on one CI failure
  • – You want to save numbers as insights

Questions

Diagnosing CI and Merge Bottlenecks skill, answered.

Is open_to_merge_seconds cycle time?

No. It mixes draft and ready time; ready_to_merge_seconds is the precise figure.

Can it rank developers?

No. Per-author numbers are cohort context, not a leaderboard.

How do I install the Diagnosing CI and Merge Bottlenecks skill?

Copy the prompt at the top into your agent. It installs the skill from PostHog/skills and sets up the habit. Or run npx skills add PostHog/skills --skill diagnosing-ci-and-merge-bottlenecks.

Is the Diagnosing CI and Merge Bottlenecks skill free?

Yes. It is published under MIT. Habit is free too.

Diagnosing CI and Merge Bottlenecks. Now as a habit.

Install the Diagnosing CI and Merge Bottlenecks skill and make it a habit: follow https://gethabit.dev/skills/posthog/diagnosing-ci-and-merge-bottlenecks.md

  • Free
  • No account
  • Undo in one line

All PostHog skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by PostHog, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.