gavel-dev
/gavel-dev
Prosi o przegląd zmian w repozytorium w interfejsie gavel, gdy użytkownik wprost tego chce albo ma stałą instrukcję takiego przeglądu.
- Autor
- photostructure ↗
- Repozytorium
- gavel ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 12.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 12.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Prosi o przegląd zmian w repozytorium w interfejsie gavel, gdy użytkownik wprost tego chce albo ma stałą instrukcję takiego przeglądu.
Oryginalny opis (EN)
Request human review of this repository's changes through a built gavel UI. Use for an explicit gavel/viewer request or standing gavel-review instruction; reserve Vite for the agent's own UI checks.
Jak działa
- Serve a built UI
- Check the UI during development
Podgląd SKILL.md
--- name: gavel-dev description: Request human review of this repository's changes through a built gavel UI. Use for an explicit gavel/viewer request or standing gavel-review instruction; reserve Vite for the agent's own UI checks. metadata: internal: true --- # Gavel development reviews in Claude Code Read [the gavel skill](../../../skills/gavel/SKILL.md) and follow its scope, grouping, comments, feedback, approval, and waiting workflow. This supplement defines how to serve reviews while developing gavel itself. ## Serve a built UI Human reviews must use built assets. A Vite page reloads whenever another session edits `src/client`, which can interrupt review and lose unsent comments. Choose the launcher before building: use the user's prescribed executable, otherwise `node dist/cli/index.js`. Resolve symlinks to identify which checkout's assets it serves; changing directories does not redirect a fixed launcher. When the launcher can serve an isolated build and other sessions are editing, build in a detached worktree at HEAD. Apply this session's uncommitted changes there before building. If a prescribed launcher is fixed to another checkout, or to this checkout while other sessions are editing it, skip the build: use its existing built assets and tell the user which checkout supplies them. This may proceed for diff review; if the review requires new UI behavior absent from that build, stop and report the build limitation. To tell whether that build matches the checkout's current tree, run `node dev/build-info.js` there and compare its `commit` and `diffHash` with **About**'s **Built from commit** and **Uncommitted changes** (`null` shows as **None**). Without a browser, run `grep -lF <value> dist/client/assets/index-*.js` in that checkout once with the `commit` and once with the `diffHash`; the build matches only when both print a file. Grep cannot check a clean tree, whose `diffHash` is `null`, so check **About** then. A match means `vite build` ran on the current tree; `pnpm build` compiles `dist/cli` just before it, but a lone `vite build` leaves `dist/cli` unchecked. A mismatch means something changed since the build, possibly only another session's edit. A build without those rows is a release build or predates them. Otherwise run `pnpm build` in the chosen checkout before opening human review. Report build failures as failures, not as the user being away. Launch from the reviewed Git root, with the shared skill's targets and flags: use a supplied patch for isolated uncommitted work or the SHA for committed work. Use the same launcher for companion commands. Share `server.ready.launchUrl`, or the detached server's `server.background.url`, including its editor-session fragment. Run `review create` and `review update` from the server's worktree: captures are bound to the repository root. Provide `- < <patch>` for each additional patch review; with neither `-` nor a redirect, creation captures that worktree's uncommitted tree. Make authorized source fixes in the owning checkout and refresh the review from the server's worktree. Committed work already on `main` uses `--no-lgtm`; commits not yet on `main` may still be approved for landing under the shared scope rules. ## Check the UI during development Use `pnpm run dev <target> [base] --no-open` only for your own UI checks in Claude's browser pane, with no extra `--` separator. It starts a foreground process tree and does not support `--background`; retain its handle. Companion commands use the API port from `server.ready`, not the Vite port. The API URL serves a development placeholder. Use the Vite UI origin printed on stderr, preserving the query and editor-session fragment from `launchUrl` when composing a URL. For human review, follow the shared skill's "Wait for feedback" section. A server launched from a Claude Code session with `node dist/cli/index.js` sends verdicts and comments to that session as an installed gavel would.
Wersje
W bazie nie ma innych skilli o nazwie gavel-dev.
Migawka bazy z 13.11.2026 · wersja paczki f2392eb013dd (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
- 100gavel
Otwiera wskazany diff w narzędziu gavel z komentarzami i proponowanym komunikatem commita na prośbę użytkownika. - 100gavel
Otwiera wskazany diff w narzędziu gavel z komentarzami przewodnika i proponowanym komunikatem commita, na prośbę użytkownika. - 100review
Przegląda pull requesty lub oczekujące zmiany w kodzie, gdy użytkownik poda link PR albo poprosi o przegląd zmian. - 100skills-pr-handle
Obsługuje pull request w repozytorium skilli Scenario, w tym komentarze z przeglądu i walidację skilli, gdy wprost o to poproszono. - 100upgrade
Migruje pliki instrukcji repozytorium do aktualnych konwencji fx-dev po wyraźnej prośbie i potwierdzeniu. - 95implementation-final-review
Przegląda ukończone zmiany implementacyjne przed końcową weryfikacją, gdy polityka repozytorium wymaga niezależnego przeglądu albo użytkownik wyraźnie o niego prosi.