Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

pr-fix

/pr-fix

Doprowadza otwarty PR do stanu czystego w pętli: czyta awarie CI i uwagi recenzentów (Codex, Architecture Review, ludzie), poprawia, zatwierdza, wypycha i czeka na boty.

Repozytorium
claude-skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
19.10.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
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

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

Licencja

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

Co robi i kiedy

Doprowadza otwarty PR do stanu czystego w pętli: czyta awarie CI i uwagi recenzentów (Codex, Architecture Review, ludzie), poprawia, zatwierdza, wypycha i czeka na boty.

Oryginalny opis (EN)

Use when the user runs /pr-fix or asks to drive an open PR to clean by looping on CI failures and reviewer feedback (Codex, the Architecture Review / SAR, humans) — read, fix, commit, push, wait for the bots, repeat. It commits and pushes on its own, so it runs only on explicit request.

Jak działa

  1. Prerequisites
  2. Process
  3. Important Notes
Sekcje z nagłówków SKILL.md, w oryginale · 141 linii, 954 słów
Podgląd SKILL.md
---
name: pr-fix
description: Use when the user runs /pr-fix or asks to drive an open PR to clean by looping on CI failures and reviewer feedback (Codex, the Architecture Review / SAR, humans) — read, fix, commit, push, wait for the bots, repeat. It commits and pushes on its own, so it runs only on explicit request.
disable-model-invocation: true
---

<SUBAGENT-STOP>
If you were dispatched as a subagent to execute a specific delegated task, do NOT follow this skill — skip it and return to the task you were given.
</SUBAGENT-STOP>

# PR Fix

You are entering an autonomous loop that drives a pull request to a clean state. Each round: read CI status + all reviewer feedback, fix what's blocking, commit, push, wait for new signal, repeat.

Reading and waiting on the bots goes through `prbots` (from the `watching-pr-bot-reviews` skill: on PATH where skillsync installed it, otherwise that skill's `bin/prbots`). Never write a `sleep` / `until` poller.

## Prerequisites

The current branch MUST have an open PR. Verify with `gh pr view --json number,state,headRefName`. If no PR exists, stop and tell the user to open one first.

## Process

### Step 1: Identify the PR

Capture once and reuse throughout the loop:

```
PR_NUMBER=$(gh pr view --json number -q .number)
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner)
NEED=codex,ci
gh api repos/$REPO/actions/workflows --jq '.workflows[].path' | grep -qi archit && NEED=$NEED,sar
```

`NEED` is what each round waits for: Codex and CI always, the SAR only when the repo has an architecture-review workflow (waiting on a SAR that never runs would sit out the timeout).

### Step 2: Run the Fix Loop

Execute up to **5 iterations**. Each iteration is one full read → fix → push → wait cycle.

#### 2a. Read PR state

1. **Bots and CI, one call:**
   ```
   prbots $PR_NUMBER --need $NEED --full
   ```
   Codex findings, the SAR, CI checks, and a CLEAN / FIX / BLOCK / PENDING verdict for HEAD. For a failing check, fetch its log:
   ```
   gh run view <run-id> --log-failed
   ```

2. **Human feedback** (prbots covers only the bots):
   ```
   gh api repos/$REPO/pulls/$PR_NUMBER/comments --paginate --jq '.[] | select(.user.type != "Bot") | {user: .user.login, path, line, created_at, body}'
   gh api repos/$REPO/pulls/$PR_NUMBER/reviews --paginate --jq '.[] | select(.user.type != "Bot") | {user: .user.login, state, submitted_at, body}'
   gh api repos/$REPO/issues/$PR_NUMBER/comments --paginate --jq '.[] | select(.user.type != "Bot") | {user: .user.login, created_at, body}'
   ```

3. **Last-commit timestamp** — anchor for distinguishing addressed vs. unaddressed human feedback:
   ```
   git log -1 --format=%cI
   ```

#### 2b. Classify the signal

- **Blocking** — everything behind a BLOCK verdict (Codex P0/P1, SAR blockers or severity ≥ 3 of 4, failing CI), a human `CHANGES_REQUESTED` review, human comments flagging correctness/security/architecture. Must fix.
- **Fix or answer** — everything behind a FIX verdict (Codex P2, SAR advisories). Fix it, or reply on the thread with the reason; a non-bot reply marks the finding handled.
- **Nice-to-have** — P3, style nits, optional suggestions. Defer and report at the end.
- **Already addressed** — bot findings prbots shows as `[replied]` / `[resolved]`; human feedback older than the last commit whose diff visibly resolves it. Skip.

A PENDING verdict is not a failure — proceed to 2d (wait).

#### 2c. Apply fixes

For each blocking item:

1. Make the code change.
2. Reference the specific comment/check being addressed in the commit message body.

When all blocking items in this round are fixed, commit and push:

```
git add <files>
git commit -m "$(cat <<'EOF'
fix: address PR feedback (round N)

- [item 1 — link to comment or check]
- [item 2 — link to comment or check]
EOF
)"
git push
```

End the message with whatever attribution trailer your environment asks for.

#### 2d. Wait for new signal

After pushing (or if no fixes were needed because everything is pending), start the wait with Bash `run_in_background: true`:

```
prbots wait $PR_NUMBER --need $NEED --trigger
```

Do not poll it: no `sleep`, no tailing its output, no re-checking with `gh`. You are notified when it exits, and its output is the digest for the next round. `--trigger` matters because neither bot re-reviews a push on its own. Exit codes:

- `0` CLEAN → go to 2e.
- `1` FIX / BLOCK → next iteration.
- `2` PENDING (timed out after 30 min, review never started, or PR closed) → stop and report; read its `x …` line for the reason.
- `3` usage / API error → stop and report.

#### 2e. Exit conditions

Stop the loop when the wait exits `0` (every needed bot reviewed HEAD, CI green, nothing open) **and** no blocking human feedback newer than the most recent commit remains.

If you hit 5 iterations without converging, stop and report the remaining blockers.

**IMPORTANT:** Work silently through iterations — do NOT spam the user with per-round status. Only emit the final summary in Step 3.

### Step 3: Report

After the loop exits, present:

#### Final Status
- **PR:** #$PR_NUMBER ($PR_URL)
- **Outcome:** `clean` | `blocked after N rounds` | `pending: <reason from prbots>`
- **Iterations:** N of 5
- **Final digest:** the last `prbots` output

#### Fixes Applied
- Round 1: [list of commits + what they addressed]
- Round 2: ...

#### Deferred (Nice-to-Haves Not Addressed)
- [suggestion]: [why deferred — usually "non-blocking" or "needs user judgment"]

#### Remaining Blockers (if outcome ≠ clean)
- [item]: [why it couldn't be auto-resolved — e.g., needs human decision, ambiguous, requires infra change]

## Important Notes

- **Bots through prbots, humans through the three `gh api` calls.** prbots reads every bot surface for HEAD; it does not report human comments.
- **Anchor on commit timestamp** to avoid re-fixing already-addressed human feedback in later rounds.
- **Never merge on PENDING.** The SAR scores severity out of 4; 3 or more blocks.
- **Never force-push** unless the user explicitly asks. Normal pushes only.
- **Never skip hooks** (`--no-verify`). If a pre-commit hook fails, fix the underlying issue.
- If feedback is ambiguous or requires a product/architecture decision, defer it and surface in the final report — do not guess.

Wersje

RepozytoriumWynikLicencja
Ta strona · smirnov-labs/claude-skills100MIT
ShieldBattery/ShieldBattery100MIT
GDriem/agent-skills100MIT
whoismdy/Code-review-ai-skills100MIT
contextgo/contextgo100Apache-2.0

Migawka bazy z 13.11.2026 · wersja paczki fedc0791b60a (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

  • 100iterate-pr
    Poprawia pull request aż do zielonego CI: naprawia błędy CI, odpowiada na uwagi z przeglądu i wypycha poprawki w automatycznym cyklu uwagi, poprawka, push, oczekiwanie.
  • 90sf-ship
    Prowadzi commit, push i pull request, odpowiada na uwagi recenzentów, pilnuje PR do scalenia i pisze notatki wydania.
  • 85address-review
    Odpowiada na uwagi z przeglądu pull requestu od ludzi i botów: poprawia kod, weryfikuje, wypycha zmiany i zamyka wątki.
  • 100goal-pr
    Doprowadza pull request do czystego stanu i scala go: uruchamia skill review-pr, naprawia uwagi średniej wagi i wyższe, powtarza do skutku, a potem scala.
  • 100pr-watch
    Doprowadza otwarty pull request do zielonego stanu: czeka na CI, rozpoznaje błędy checków i odpowiada na komentarze botów review, stosując jedną obserwację w tle na cykl.
  • 100babysit-pr
    Prowadzi otwarty pull request do stanu gotowego do scalenia: obserwuje CI, ocenia uwagi z przeglądu względem kodu, wypycha poprawki i utrzymuje gałąź aktualną.

Uwagi i zgłoszenia

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