om-pipeline-retro

Classify finished pull request pipeline runs and rank rework causes by wall-clock hours.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-pipeline-retro-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-pipeline-retro
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-pipeline-retro
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-pipeline-retro-tkogut

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes references (resource) components.

What problem does it solve? Teams running automated PR pipelines often cannot tell how many changes merged in a single pass versus how many needed expensive second passes, or what caused the rework. This Skill reads finished pull requests from the configured tracker, deterministically classifies each run (clean single pass, hard recovery, loop checkpoints, or unexplained), and ranks the recorded causes by the wall-clock hours they cost beyond the median clean run. ## Core Features & Use Cases - Deterministic run classification: A shell classifier (references/classify-runs.sh) parses agent marker comments, reviews, and timestamps to assign each finished PR a class, never relying on model judgement. - Cost-ranked cause report: Causes are ranked by excess hours beyond the clean-run baseline, with coverage disclosures for missing timestamps, sizes, and truncated windows. - Read-only with handoff: The Skill never merges, edits, comments, or labels anything; it offers to pass the top cause to om-prepare-issue for filing. - Use Case: Ask "why is our pipeline slow" and get a report showing that 62% of runs finished in one pass, merge conflicts cost 14 hours beyond baseline across 5 PRs, and 3 second passes have no recorded cause. ## Quick Start Ask the agent to run a pipeline retro over the last 30 days of pull requests and rank what the second passes cost in hours.

Frequently Asked Questions about om-pipeline-retro

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

FAQPage Schema
How do I measure how often my PR pipeline needs a second pass?▼

Run this Skill with an optional --since date and --limit; it lists merged and closed-unmerged pull requests from the tracker, classifies each via the deterministic classifier script, and reports the share of clean single-pass runs plus the ranked causes of second passes.

What data does the pipeline retro classifier use to classify runs?▼

It uses agent-authored marker comments, review states and bodies, labels, and open/merge/close timestamps fetched via the tracker's list-prs and get-pr operations. Quoted lines and fenced blocks are stripped so human quotes of bot text never create false runs or causes.

Does the pipeline retro skill modify pull requests or labels?▼

No, it is read-only end to end: it never merges, edits, comments on, or labels anything. After reporting, it only offers to hand the top-ranked cause to om-prepare-issue, and filing remains the user's decision.

What happens when a second pass has no recorded cause?▼

The run is classified as unexplained rather than guessed at, and its cost is still counted. The report highlights the unexplained count because it measures what the pipeline runs themselves failed to record.

Why does the retro report say run counts are an upper bound?▼

When marker comments lack timestamps, skills that post no opening comment cannot be time-clustered, so each marker comment counts as its own run. The classifier's timestampCoverage note discloses this and the report leads with that limitation.

Can I run the pipeline retro without jq installed?▼

The classifier script requires jq and exits with an error if it is missing. When the harness cannot execute shell at all, the agent applies the classification rules documented in the script's comment header inline and states that in the report.