How do I install the Fetch Tide Pr Status skill?

Run npx skillmds@latest add openshift-eng/fetch-tide-pr-status in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fetch Tide Pr Status safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fetch Tide Pr Status?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fetch Tide Pr Status free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fetch Tide Pr Status?

openshift-eng (@openshift-eng) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fetch Tide Pr Status by openshift-eng

Name: Fetch Tide Pr Status
Rating: 4.5 (4 reviews)
Author: openshift-eng

File contents

Fetch Tide PR Status

CLI equivalent of the Prow PR Status page. Focuses on labels and required jobs — the most common merge blockers. Tide also checks other things (author, milestone) which may appear in the tide verdict but are not broken out here.

Only outputs open, non-draft PRs.

Prerequisites

gh CLI authenticated
python3 with pyyaml (pip install pyyaml)

Usage

# All open PRs by an author
python3 "${SKILL_DIR}/fetch_tide_pr_status.py" openshift/cluster-monitoring-operator machine424

# Specific PRs
python3 "${SKILL_DIR}/fetch_tide_pr_status.py" openshift/cluster-monitoring-operator 3057,3044

Output

JSON array, one object per PR:

[
  {
    "number": 3044,
    "title": "OCPBUGS-105305: [release-4.21] wrap ...",
    "author": "machine424",
    "url": "https://github.com/openshift/cluster-monitoring-operator/pull/3044",
    "branch": "release-4.21",
    "state": "open",
    "mergeable": true,
    "tide": "Not mergeable. Needs jira/valid-bug label.",
    "blockers": [
      "missing required label: jira/valid-bug",
      "has forbidden label: jira/invalid-bug",
      "job not passing: ci/prow/e2e-aws-ovn (running)"
    ],
    "labels": {
      "met": false,
      "required": {
        "have": ["lgtm", "approved"],
        "missing": ["jira/valid-bug"]
      },
      "forbidden": {
        "have": ["jira/invalid-bug"],
        "clear": ["needs-rebase", "do-not-merge/hold"]
      }
    },
    "required_jobs": [
      {"name": "ci/prow/unit", "state": "success"},
      {"name": "ci/prow/e2e-aws-ovn", "state": "running", "description": "Job triggered."}
    ]
  }
]

tide — Tide's own verdict. blockers — what's preventing merge. required_jobs — non-optional jobs from openshift/release config; if the config could not be fetched, contains a single {"error": "..."} entry instead of jobs (not reflected in blockers).

Data Sources

https://prow.ci.openshift.org/tide.js — required/forbidden labels (public)
gh api repos/{o}/{r}/pulls/{n} — PR metadata
gh api repos/{o}/{r}/commits/{sha}/status — job statuses + Tide context
raw.githubusercontent.com/openshift/release/master/ci-operator/jobs/... — presubmit config (required vs optional)

---name: fetch-tide-pr-statusdescription: Use when checking what's blocking a PR from merging in OpenShift CI — evaluates Tide merge requirements, required/forbidden labels, and required job statuses.---# Fetch Tide PR StatusCLI equivalent of the [Prow PR Status page](https://prow.ci.openshift.org/pr). Focuses on labels and required jobs — the most common merge blockers. Tide also checks other things (author, milestone) which may appear in the `tide` verdict but are not broken out here.Only outputs open, non-draft PRs.## Prerequisites- `gh` CLI authenticated- `python3` with `pyyaml` (`pip install pyyaml`)## Usage```bash# All open PRs by an authorpython3 "${SKILL_DIR}/fetch_tide_pr_status.py" openshift/cluster-monitoring-operator machine424# Specific PRspython3 "${SKILL_DIR}/fetch_tide_pr_status.py" openshift/cluster-monitoring-operator 3057,3044```## OutputJSON array, one object per PR:```json[ { "number": 3044, "title": "OCPBUGS-105305: [release-4.21] wrap ...", "author": "machine424", "url": "https://github.com/openshift/cluster-monitoring-operator/pull/3044", "branch": "release-4.21", "state": "open", "mergeable": true, "tide": "Not mergeable. Needs jira/valid-bug label.", "blockers": [ "missing required label: jira/valid-bug", "has forbidden label: jira/invalid-bug", "job not passing: ci/prow/e2e-aws-ovn (running)" ], "labels": { "met": false, "required": { "have": ["lgtm", "approved"], "missing": ["jira/valid-bug"] }, "forbidden": { "have": ["jira/invalid-bug"], "clear": ["needs-rebase", "do-not-merge/hold"] } }, "required_jobs": [ {"name": "ci/prow/unit", "state": "success"}, {"name": "ci/prow/e2e-aws-ovn", "state": "running", "description": "Job triggered."} ] }]```**`tide`** — Tide's own verdict. **`blockers`** — what's preventing merge. **`required_jobs`** — non-optional jobs from openshift/release config; if the config could not be fetched, contains a single `{"error": "..."}` entry instead of jobs (not reflected in `blockers`).## Data Sources- `https://prow.ci.openshift.org/tide.js` — required/forbidden labels (public)- `gh api repos/{o}/{r}/pulls/{n}` — PR metadata- `gh api repos/{o}/{r}/commits/{sha}/status` — job statuses + Tide context- `raw.githubusercontent.com/openshift/release/master/ci-operator/jobs/...` — presubmit config (required vs optional)

Frequently asked questions

Fetch Tide Pr Status