Reports repository position in the review-to-merge pipeline and names the next command.
npx skills add https://github.com/PeteRichardson/skills --skill pipeline-peterichardson
Please help me install this Agent Skill. Skill: pipeline Source: https://github.com/PeteRichardson/skills/tree/main/pipeline Command: npx skills add https://github.com/PeteRichardson/skills --skill pipeline-peterichardson
pipeline-status script to count reviews, open issues, triage snapshots, in-flight branches, merge orders, and merged PRs across six stages. - Subcommand modes: /pipeline for the full dashboard, /pipeline next for just the next command, /pipeline brief for an instant cheat sheet with no API calls, /pipeline blocked for only items awaiting a human decision, and /pipeline doc to locate the workflow documentation. - Judgment layer: Reads NEEDS-DECISION questions, semantic-collision warnings in merge orders, and stale-review drift to override the script's mechanical next-step cascade when warranted. - Use Case: After merging a PR in the browser and returning to your terminal, run /pipeline to see the dashboard recomputed from live artifacts and learn that two issues need decisions before re-running issue triage. ## Quick Start Ask the assistant to run /pipeline to show where this repository stands in the review-to-merge workflow and what command to run next.High-intent search queries and answers about installing and using this skill.
Run /pipeline to get a dashboard of all six stages computed from artifacts like review reports, issue labels, branches, and PRs. It ends with a next: line naming the exact command to type, such as re-running issue triage.
This Skill detects progress from durable artifacts each stage leaves behind: docs/reviews files, source: issue labels, .claude/tmp snapshots, Fix-I<n> branches, and merged PRs. Because artifacts are written by the stages themselves, the status cannot disagree with reality after out-of-band merges.
Yes, pass -n or let it degrade automatically when gh or jq is missing. Offline mode reports GitHub-dependent stages (issues, PRs, merge order staleness, merges) as unknown rather than as empty, so local stages still show accurate counts.
No, it is advisory only and never runs any pipeline stage, including merges. It names the next command for you to type yourself, which keeps stage transitions and especially merging a deliberate manual action.
Stage-4 work is only visible on branches matching the Fix-I<n> naming convention, review staleness is measured in commit count which over-reports on docs-heavy churn, and multi-repo status across projects is not supported.
signalfxGenerate Splunk Observability Cloud detector Terraform from otel-audit reports.
spiriMirrorFix GitHub issues through branching, testing, and pull request workflow.
U1traVenoMove GitHub issues and external PRs through a triage state machine with agent-ready briefs.
papeete-consulting-labGenerate a kanban board from task files with derived workflow states.