Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

pr-open

/pr-open

Otwiera pull request gałęzi jako wersję roboczą lub gotową zgodnie z polityką PR, a opis zaczyna od wniosku i odpowiada na pytania: dlaczego, co, jak.

Repozytorium
harness ↗
Licencja
MIT
Ostatnia zmiana repozytorium
13.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
3
Skrypty
1
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co sprawdzić przed instalacją
  • 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.

Skrypty: pr_open_test.go

Co robi i kiedy

Otwiera pull request gałęzi jako wersję roboczą lub gotową zgodnie z polityką PR, a opis zaczyna od wniosku i odpowiada na pytania: dlaczego, co, jak.

Argumenty

/pr-open [base branch]
Oryginalny opis (EN)

Opens the pull request of a branch, as a draft or ready by the pull request policy, or edits its body. The body starts with a bottom line, then answers Why, What and How, in this order. How holds the plan diagrams and the visuals of the done tasks. Use in the ship step of the harness loop, or when the user types /90p:pr-open (Codex: $90p:pr-open).

Jak działa

  1. Decision tree
  2. Binary
  3. 1. Collect the sources
  4. 2. Pick the visuals
  5. 3. Write the body
  6. 4. Open or edit the pull request
Sekcje z nagłówków SKILL.md, w oryginale · 107 linii, 1 253 słów
Podgląd SKILL.md
---
name: pr-open
description: "Opens the pull request of a branch, as a draft or ready by the pull request policy, or edits its body. The body starts with a bottom line, then answers Why, What and How, in this order. How holds the plan diagrams and the visuals of the done tasks. Use in the ship step of the harness loop, or when the user types /90p:pr-open (Codex: $90p:pr-open)."
argument-hint: "[base branch]"
---

# Open a pull request

A reviewer reads the body before the diff. The body starts with a bottom line. Then it answers three questions, in this order: Why, What and How. The guard rule `pr-body-shape` denies another shape.

Arguments: `$ARGUMENTS`

## Decision tree

```
Start: run harness version ("Binary"), then step 1
├── harness run status shows a run → step 2 keeps the plan diagrams and adds the visuals of the done tasks
├── no run → step 2 applies the visual table to the changed files
├── a UI change → the wireframe row of the visual table
├── a visual to draw → references/visuals.md shows each kind
├── no pull request for the branch → step 4 creates it, as a draft or ready by the policy
├── a merged or closed pull request for the branch → step 4 creates a new one by the policy
├── an open pull request → step 4 edits its body
└── the guard denies the body → fix the body file of step 3, and run the command again
```

## Binary

- In each command below, `harness` means the full path `"${CLAUDE_PLUGIN_ROOT}/bin/harness"`. Write the full path in each command.
- On Codex, `${CLAUDE_PLUGIN_ROOT}` shows unexpanded. Use `bin/harness` two folders above this `SKILL.md`.
- Run `harness version` first. If it fails, stop and report the error. Skip it when the harness skill started this skill: the loop already ran it.

## 1. Collect the sources

1. The base is the argument. With no argument, it is the `PR sequence` base of the plan, else `git.default_branch` of `.harness.yaml`.
2. Run `harness run status`. Its first line is `run <id> phase=...`. The plan is `.harness/runs/<id>/plan.md`. With `active: no`, there is no plan. Skip the command when you hold the run id from the harness loop.
3. Read the commits: `git log --format='%h %s' <base>..HEAD`.
4. A done task is a plan task whose `### Commits` line has the subject of a commit in that log. That line names the task with `(task n)`. The commit subject has no `(task n)`.
5. Read the changed files: `git diff --name-only <base>...HEAD`. Read the diff of each file that a reviewer must understand.

## 2. Pick the visuals

- Read the `mermaid` fences of the plan, each under its `### ` heading of `## Tech specs`.
- Keep a diagram when the diff changes a file of its section: the `Code: task n` line names the tasks, and each task names its owned files.
- Drop a diagram when the diff changes none of its files.
- Copy a kept fence as it is. Its marks show what is new, changed and removed.
- Add each visual that a done task needs and the plan lacks. With no plan, use the changed files. Pick it from this table. `references/visuals.md` has an example of each.

| Kind of change | Visual |
| --- | --- |
| A state or phase change | `stateDiagram-v2` |
| A new command, hook or pipeline | `flowchart` |
| A call across processes, an HTTP edge or a consumer | `sequenceDiagram` |
| A user-facing flow: the steps of a CLI command, a page flow | `journey` |
| A UI change | A wireframe in a `text` fence |
| A domain model or contract change | `classDiagram` |
| A schema change | `erDiagram` |

- Pipe a new state, flow, class or ER visual to `harness diagram` and paste its output. The guard denies an unmarked one.
- A `sequenceDiagram` and a `journey` take no mark. Paste each in a plain `mermaid` fence.
- Do not link the plan `.excalidraw` sketch. `.harness/runs/<id>/` is not in git. Copy its layout in the text wireframe.

## 3. Write the body

Run `harness pr body --base <base>` with the base of step 1. It prints the skeleton with the bottom line and Why placeholders. What has one bullet for each branch commit, and How has the `mermaid` fences of the plan. Write its output in a file `pr-body.md` in the scratchpad, or in the temp dir on a host with none. Keep its absolute path, `<body>` below. Do not write it in the repository.

Replace the two placeholders. Keep the fences as the command printed them. Edit a What bullet only when the diff needs a clearer name. Add the visuals of step 2 that the plan lacks.

```
<bottom line: what the PR changes and what the reviewer must check>

## Why

<why: the problem and the reason for the change>

## What

- <one bullet for each branch commit, printed by the command>

## How

The change adds no diagram.
```

- Write the body BLUF (bottom line up front). The bottom line is one or two sentences in one line. Each section starts with its main point.
- `## Why`: two to four sentences. Name the problem first. Use the plan `## Goal` and the decisions that a reviewer can question.
- `## What`: the command prints one bullet for each commit, in the order of the commits. Edit a bullet only when the diff needs a clearer name.
- `## How`: the mechanism. Put a visual of step 2 where it explains faster than text. Put one sentence above each visual: its main point.
- A How with no visual says why in one sentence.
- A line outside a fence has 40 words at most. A table row is one line.
- Use no em dash and no emoji.

## 4. Open or edit the pull request

1. Run `harness pr policy`. It prints `draft: required` or `draft: optional`, then `merge: user` or `merge: agent`. If `harness pr policy` fails, keep the draft, and the user merges.
2. Run `harness verify --commits <base>`. The guard denies a push and a create before it passes.
3. Run `harness pr check --body-file <literal absolute path of the body file>`. Fix every problem that it prints. Write the path as a literal, not as a variable.
4. Push the branch: `git push -u origin HEAD`.
5. Run `gh pr view --json url,state,isDraft`. A failed call means no pull request. Only with `state` `OPEN`, run `gh pr edit <url> --body-file <body>`, with the `url` field.
6. With no pull request, or with a `MERGED` or `CLOSED` one, create it by the `draft` line of the policy.
   - `draft: required`, or a failed policy: run `gh pr create --draft --base <base> --title "<the first commit subject>" --body-file <body>`.
   - `draft: optional`: run the same command without `--draft`.
7. With `draft: optional` and an open draft, run `gh pr ready <url>`. With `draft: required`, leave the draft as it is.
8. Act on the `merge` line, after the create or the ready.
   - `draft: required` with `merge: agent`: report the URL. The user marks it ready and merges, because the guard denies `gh pr ready`.
   - A failed `harness pr policy`: report the URL. The user merges.
   - `merge: user`: report the URL. The user merges.
   - `draft: optional` with `merge: agent`: run `gh pr checks <url>`. Only when it exits 0, run `gh pr merge <url> --squash`. A failed, pending or missing check means stop and report.
9. Report the URL and the state. The merge comes before `harness run report` and `harness run done --pr <url>` of the harness skill.

When the guard denies the body, read the reason, fix the body file and run the command again.
Pliki w paczce (3)
  • SKILL.md 7 KB
  • pr_open_test.go 11 KB
  • references/visuals.md 3 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · 90p-labs/harness100MIT
bklit/bklit-ui100MIT
grixu/cc-toolkit100MIT

Migawka bazy z 13.11.2026 · wersja paczki 3dadadb6e23a (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100pr
    Pisze tytuł i opis pull requestu w języku zrozumiałym dla ludzi, pokazuje szkic i dopiero potem otwiera wersję roboczą.
  • 100open-pr
    Otwiera lub aktualizuje pull request w agentic-seo-check: sprawdza bramki, ustala tytuł, wypełnia opis z szablonu i status szkicu.
  • 844-open-pr
    Otwiera lub aktualizuje pull request dla bieżącej funkcji, gdy użytkownik o to prosi.
  • 100create-pr
    Otwiera lub aktualizuje pull request na GitHubie dla bieżącej gałęzi, także z wypchnięciem zmian.
  • 96pr
    Otwiera pull request, gdy użytkownik o to prosi, i przygotowuje jego tytuł oraz opis.
  • 90open-pr
    Aktualizuje gałąź, wypycha ją i otwiera pull request do zgłoszenia w formacie repozytorium, a potem obserwuje CI.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.