# Dyl Ready PR

Get a PR merge-ready for Dylan: deep /dyl-review till 🟢, mark it ready, resolve...

- Repository: https://github.com/cursor/plugins (15000 stars)
- Category: Git and review
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add cursor/plugins --skill dyl-ready-pr -g -a claude-code -y`
Codex: `npx skills add cursor/plugins --skill dyl-ready-pr -g -a codex -y`
Cursor: `npx skills add cursor/plugins --skill dyl-ready-pr -g -a cursor -y`
Gemini CLI: `npx skills add cursor/plugins --skill dyl-ready-pr -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add cursor/plugins`

## Description

Get a PR merge-ready for Dylan: deep /dyl-review till 🟢, mark it ready, resolve conflicts, then babysit CI and comments. Use for /dyl-ready-pr, "get PR green", "make the PR mergeable", "/dyl-review till green then ready", or ready-to-merge asks under /dyl-mode.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Dyl ready PR

Strict sequence to get **one** PR merge-ready.

**Requires** `pstack`, `cursor-team-kit`, and `thermos`. Check first with [../dyl-mode/references/requirements.md](../dyl-mode/references/requirements.md). Missing → stop and tell the user to run `/add-plugin <name>`.

Trigger phrases that **must** run this skill (not plain Babysit): "get PR green", "get it green", "make the PR mergeable", "ready the PR", `/dyl-ready-pr`, "`/dyl-review` till green, then `/dyl-ready-pr`".

**Merge-ready** is what "get PR green" means. All of these hold on the current HEAD, or it is not merge-ready.

- The latest `/dyl-review` is 🟢.
- Marked ready for review, not draft.
- No merge conflicts with its base branch.
- Every check has run and passed, required or not, Bugbot included when the repo runs it.
- Every review thread is resolved. One left for the human is a stop, so report it.

## Sequence (apply strictly)

Two phases, in order: **review till 🟢** → **drive to merge-ready**. Step 0 decides whether Phase 1 is already done. Phase 2 always runs.

### Step 0. Classify

Inspect the target PR (default: the PR for the current branch).

**Small and low-risk** means: typo/copy, comment, import sort, one-line lint, lockfile noise, or an equivalent tweak that cannot reasonably introduce new logic bugs. Behavior, control flow, types, UI structure, flags, or more than a tiny surface area is not small.

Skip Phase 1 only when its exit was already reached on this PR in this conversation (or a cited prior run): a **deep** `/dyl-review` ran, the latest `/dyl-review` is 🟢, and every change since the last deep pass is small and low-risk. When unsure, run it.

Say which phases you are running and why in one sentence before acting.

### Phase 1. Review till 🟢

Run the `dyl-review` skill at **deep** depth against the PR. Then:

The rest: https://github.com/cursor/plugins/blob/HEAD/dyl-stack/skills/dyl-ready-pr/SKILL.md