review-changes
/review-changes
Pomaga samodzielnie sprawdzić zmiany przed otwarciem pull requestu i dobrać potrzebnych recenzentów.
- Autor
- svelasquezr ↗
- Repozytorium
- mash-workbench-marketplace ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 05.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 12
- Skrypty
- 10
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 05.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 10 skryptów w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: find-checks.sh, reviewers-for-change.py, route_change.py, route_check.py, route_config.py, route_explain.py, route_guards.py, route_models.py, route_rules.py, route_types.py
Co robi i kiedy
Pomaga samodzielnie sprawdzić zmiany przed otwarciem pull requestu i dobrać potrzebnych recenzentów.
Oryginalny opis (EN)
Use when you are about to open a pull request or share a branch, when asked to review or self-review your changes, or when deciding which reviewer agents a change needs
Jak działa
- Steps
Podgląd SKILL.md
---
name: review-changes
description: Use when you are about to open a pull request or share a branch, when asked to review or self-review your changes, or when deciding which reviewer agents a change needs
---
# Review your changes before opening a PR
Reviews committed work with the agents the project's routing (`.claude/reviewers.toml`) names. It needs only git and writes nothing to a PR. Below, `route` means `python3 <this skill's base directory>/reviewers-for-change.py`, run from the repository.
**Reviewers judge; tools enforce.** Whatever a tool can decide belongs in automation, not in a reviewer's attention.
## Steps
0. **Does this change fix a bug that a review passed?** Ask for its issue link and record it ("Recording escapes" in `<this skill's base directory>/reference.md`).
1. **Range and reviewers.** Review `<default branch>...HEAD` (`origin/HEAD`, else `origin/main` or `origin/master`, else local `main` or `master`, else ask) unless the user names another base. Uncommitted changes: ask the user to commit first. `route <range> --models` prints `agent<TAB>model` lines. A non-zero exit means the range or config is wrong, never "no reviewers". Dispatch every agent printed: its name as `subagent_type`, its model as `model` unless `-` (the agent's default; `general-purpose`: `sonnet`). With no `.claude/reviewers.toml` only `review-routing:change-reviewer` is printed: say add-reviewer sets up routing. When the change touches `.claude/reviewers.toml` or `.claude/agents/`, also run `route --check`.
2. **Checks first, once, as a gate.** Use the test, lint and format commands that CLAUDE.md or AGENTS.md names. If none: `bash <this skill's base directory>/find-checks.sh <repo-root>` lists candidates (if it fails, treat the list as empty); propose them, run only what the user confirms, then offer a CLAUDE.md line naming them. If nothing exists, review anyway: tell reviewers "no automated checks ran", pair mechanical findings with the tool that would catch them, and report **Unchecked: no tests or linters configured**. Fix any failure before step 3.
3. **Dispatch all reviewers in one message.** Each prompt holds: the range to review (`git diff <range>`), what the change is for in one or two sentences, the check results, and anything the agent's description says the caller must name. For `general-purpose`, first add "General-purpose reviewer prompt" from the reference. A reviewer that errors or gives no verdict is dispatched again, never counted as safe.
4. **Triage every finding.**
- Mechanical: fix it and add (or propose) the check that now covers it. With mash-workbench, record it with `scout`.
- Introduced by this change: fix in a new commit (no amend), rerun the checks, then send the fix round to the reviewers ("Fix rounds" in the reference). After two rounds still `NOT SAFE`, stop and report the open findings.
- A finding you think is wrong: answer it with evidence in that reviewer's next prompt; its verdict decides.
- Pre-existing: list it for the user; file nothing. Record each `escape: yes` once the user gives an issue link.
5. **Summary, in the terminal only:** each reviewer's last verdict, Critical / Important / Minor counts and fix rounds; the checks that ran or the Unchecked line; open Minor suggestions; Pre-existing findings. Say "ready to open your PR" only when every last verdict is `SAFE TO LAND`; otherwise list what is open. Never push, open a PR, comment or merge.
Pliki w paczce (12)
- SKILL.md 3 KB
- find-checks.sh 4 KB
- reference.md 6 KB
- reviewers-for-change.py 10 KB
- route_change.py 4 KB
- route_check.py 5 KB
- route_config.py 13 KB
- route_explain.py 4 KB
- route_guards.py 6 KB
- route_models.py 4 KB
- route_rules.py 4 KB
- route_types.py 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · svelasquezr/mash-workbench-marketplace | 90 | MIT |
| grixu/cc-toolkit | 100 | MIT |
| joshgons/agent-skills | 100 | MIT |
| rimega92/Engineering-Skills | 100 | MIT |
| eldrego/claude-dev-workflow | 100 | MIT |
| ncosentino/needlr | 100 | MIT |
| jerelvelarde/chalk-skills | 100 | MIT |
| Pluneto/skills | 90 | MIT |
| doist/todoist-cli | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki e69b446314dc (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
- 96code-review
Przeprowadza przegląd kodu zmiany, gałęzi lub pull requestu na prośbę użytkownika. - 95ai-review
Przegląda lokalne zmiany w kodzie wieloagentowym recenzentem: niezatwierdzone zmiany, zmiany w stage lub przed otwarciem PR. - 100review-loop
Sprawdza zmianę modelem od innego dostawcy w pętli, aż ją zatwierdzi, a także przed otwarciem pull requestu. - 100review-pr
Przegląda pull requesty na GitHubie za pomocą uporządkowanej analizy kodu, gdy trzeba sprawdzić PR albo audytować zmiany. - 100review-pr
Przegląda pull request pod kątem jakości kodu i problemów bezpieczeństwa. - 96code-review
Przegląda pull requesty w GitHub CLI (gh) i pomaga sprawdzić zmiany przed scaleniem.