walk-the-diff
/walk-the-diff
Prowadzi interaktywnie przez lokalne zmiany w kodzie przed lub zamiast przeglądu PR, pokazując każdą zmianę po kolei.
- Autor
- sandsower ↗
- Repozytorium
- beislid ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 30.08.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 5
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 30.08.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
Prowadzi interaktywnie przez lokalne zmiany w kodzie przed lub zamiast przeglądu PR, pokazując każdą zmianę po kolei.
Wyzwalacze z opisu
Oryginalny opis (EN)
Use when the user wants to walk through their local changes interactively before or instead of a PR review — e.g., "guided review", "walk me through the changes", "review my branch", "let's go through the diff". Also use when the user explicitly invokes the walk-the-diff skill through the host agent. This is for interactive human-facing walkthroughs of code changes, not automated code review.
Jak działa
- Global interactive contract
- JIT phase protocol
- Checklist and outputs
- Visual walkthrough artifact
- Global tripwires
- Common mistakes
- Key principles
Podgląd SKILL.md
--- name: walk-the-diff description: Use when the user wants to walk through their local changes interactively before or instead of a PR review — e.g., "guided review", "walk me through the changes", "review my branch", "let's go through the diff". Also use when the user explicitly invokes the walk-the-diff skill through the host agent. This is for interactive human-facing walkthroughs of code changes, not automated code review. --- # Guided Review Simulate sitting next to a colleague who wrote the code and having them walk you through the changes. Present diffs in a logical order with context about why each change was made, highlight decision points and scrutiny areas, then pause so the reviewer can ask questions before moving on. **Don't use this for:** automated review findings, PR comment posting, fixing feedback, or durable visual reports. Use `review`, `pr-patrol`, `review-response`, or explicit `show-me` instead. ## Global interactive contract You are the author/presenter, not the reviewer. Explain and defend the change honestly without preemptively rejecting your own code. The chunk gate is mandatory: never present a new chunk until the reviewer explicitly selects `Move on` or `Flag for follow-up`. If the reviewer types free text, treat it as a question/comment, answer it, present the same three options again, and stop. The three options at every pause are exactly: - `Move on` — advance to the next chunk - `I have questions` — stay on this chunk; the reviewer will type their question next - `Flag for follow-up` — note this chunk as needing revisit, then advance ## JIT phase protocol Walk-the-diff phases are authoritative only after their aux files are read. Complete phases in order. At each phase boundary, read the matching file and follow it. If a phase file cannot be read, hard-fail instead of continuing from memory: > 🛑 Could not read `skills/walk-the-diff/<phase-file>.md`. Walk-the-diff cannot safely execute this phase from memory; reinstall Beislið or restore the file. - Phase 1: `skills/walk-the-diff/phase-1-context.md` - Phase 2: `skills/walk-the-diff/phase-2-tour-plan.md` - Phase 3: `skills/walk-the-diff/phase-3-present.md` - Phase 4: `skills/walk-the-diff/phase-4-wrap.md` When `BEISLID_VERBOSE=1`, print one aux load stamp after successfully reading each phase file. Stamp format is `✓ walk-the-diff/<phase-file-stem> v1 loaded` for `phase-1-context`, `phase-2-tour-plan`, `phase-3-present`, and `phase-4-wrap`. ## Checklist and outputs 1. **Gather context** — read `phase-1-context.md`. Outputs: base branch/merge base, commits, linked ticket/plans/specs, matching `break_spec_approved`, `spec_approved`, or `blueprint_approved` latest pointer entries when present, changed files, surrounding-code notes. 2. **Plan the tour** — read `phase-2-tour-plan.md`. Outputs: ordered chunk list, grouping rationale, reviewer preference if asked. 3. **Present chunks** — read `phase-3-present.md`. Outputs: each reviewed chunk, questions answered, flags/open items, reviewer gate choices. 4. **Wrap up** — read `phase-4-wrap.md` only after all chunks are reviewed or flagged. Outputs: overall feedback, saved feedback doc path, final stop. ## Visual walkthrough artifact If the user explicitly wants a durable visual walkthrough, proof deck, or local HTML report instead of an interactive chunk-by-chunk review, invoke `show-me`. Do not run `show-me` automatically; it is manual/user-requested only in v1. ## Global tripwires - One chunk at a time; never dump the whole diff. - Do not advance on silence, ambiguity, or free-text approval. Require `Move on` or `Flag for follow-up`. - Read commits and surrounding code before presenting diffs. - Save feedback docs in user state, not the repo. - Do not fix, implement, commit, push, or act on feedback during or after the walkthrough. - After Phase 4 saves feedback, stop. Acting on feedback is a separate conversation. ## Common mistakes - Presenting all chunks at once. - Critiquing the code instead of explaining it as the author. - Skipping context gathering and showing raw diffs without intent. - Only reading diffs, not surrounding code. - Advancing without the explicit chunk-gate choice. - Fixing code during the review. - Acting on feedback after wrap-up. ## Key principles - Interactive pacing beats completeness dumps. - Be honest about uncertainty; do not invent rationale missing from commits or plans. - Adapt depth to reviewer questions. - The feedback doc is the deliverable.
Pliki w paczce (5)
- SKILL.md 4 KB
- phase-1-context.md 2 KB
- phase-2-tour-plan.md 2 KB
- phase-3-present.md 3 KB
- phase-4-wrap.md 2 KB
Wersje
W bazie nie ma innych skilli o nazwie walk-the-diff.
Migawka bazy z 13.11.2026 · wersja paczki b077c124213f (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
- 100code-review
Prowadzi interaktywny przegląd zmian z PR lub lokalnego diffa i pokazuje każde znalezisko po kolei, aby można je zastosować, zmodyfikować, odłożyć lub odrzucić. - 90walk-with-me
Przeprowadza użytkownika przez kod krok po kroku jako code walk zamiast raportu, na przykład przy prośbie o wyjaśnienie bazy kodu. - 100wd-review
Otwiera przeglądarkę różnic wd, żeby użytkownik sam przejrzał zmiany, a interaktywną pętlę uruchamia tylko na wyraźną prośbę. - 90review-speedread
Pokazuje człowiekowi kształt zmiany, zanim ten przeczyta diff, jako szybki przegląd bez pełnego raportu ustaleń. - 90code-review
Recenzuje zmiany w kodzie, takie jak pull request, diff czy commit, i podaje konkretne uwagi możliwe do wdrożenia. - 90aped-checkpoint
Przechodzi po zmianach w kodzie i wyjaśnia diff: co się stało i jakie zmiany weszły, bez dashboardu postępu sprintu.