code-review
/code-review
Przeprowadza code review PR, MR i diffów w strukturze kanapki, motywująco, z wyraźnym rozdzieleniem blockerów od drobnych uwag.
- Autor
- freema ↗
- Repozytorium
- ai-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 25.10.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 25.10.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
Przeprowadza code review PR, MR i diffów w strukturze kanapki, motywująco, z wyraźnym rozdzieleniem blockerów od drobnych uwag.
Wyzwalacze z opisu
Oryginalny opis (EN)
Sandwich-structured code review for PRs, MRs, diffs, or pasted code. Triggers on: "review this", "check my PR/MR", "what do you think of this code", "is this OK to merge", or any paste of code/diff where the user wants feedback. Produces motivating reviews that clearly separate blockers from nitpicks. Always use this skill — even for quick reviews. The structure matters.
Jak działa
- The Sandwich Method (always follow this order)
- Tone Guidelines
- Example Output Structure
- Edge Cases
Podgląd SKILL.md
--- name: code-review description: > Sandwich-structured code review for PRs, MRs, diffs, or pasted code. Triggers on: "review this", "check my PR/MR", "what do you think of this code", "is this OK to merge", or any paste of code/diff where the user wants feedback. Produces motivating reviews that clearly separate blockers from nitpicks. Always use this skill — even for quick reviews. The structure matters. --- # Code Review Skill Goal: leave the author feeling **capable and motivated**, not defensive. The review should make them think "yes, I'm on the right track, let me fix that one thing." --- ## The Sandwich Method (always follow this order) ### Top Slice — Overall - Open with genuine recognition of what's good - Name the design pattern or approach and why it's solid - One short paragraph, no hedging, no "but..." - Example: *"Separating analytics into its own component via CustomEvents is a clean SRP refactor — event-driven decoupling between components is well-designed here."* ### Filling — Bugs & Notes #### Bug / Blocker (must fix before merge) - State the bug clearly and directly - Show the broken code, explain WHY it's wrong - Provide the fix — exact code, not vague direction - One blocker per section. If there are multiple, list them all here. #### Minor Notes (optional, low pressure) - Numbered list - Each note: what it is + why it matters (or why it's just a preference) - Explicitly label style preferences vs. real issues: *"Style preference, not a bug — current approach works."* - Include positive observations too (e.g., "No double-fire risk — verified both paths are cleanly separated.") ### Bottom Slice — Verdict - Clear, confident closing statement - Name the blocker(s) and say everything else is solid - Example: *"Bug with `id` is the only blocker. The rest is clean and well thought-out."* - Optional: one motivating sentence — not sycophantic, just human --- ## Tone Guidelines - **Direct, not harsh.** Say "this is wrong" not "you might want to consider..." - **Specific, not vague.** Always show code. Never say "the naming could be better" without showing the fix. - **Proportional.** A 5-line nit doesn't get 3 paragraphs. - **Honest about preferences.** If it's a style preference, say so. Don't dress up opinions as bugs. - **Push, don't crush.** The goal is the author merging better code AND feeling good about it. --- ## Example Output Structure ``` ## Overall [positive opening paragraph about the approach] ## Bug [blocker description] [broken code snippet] [fix snippet] ## Minor Notes 1. [note with label: bug / style preference / positive observation] 2. ... ## Verdict [confident closing + blocker summary] ``` --- ## Edge Cases - **No bugs found?** Still follow the sandwich. The filling becomes only minor notes. - **Multiple blockers?** List all under "Bug / Blocker". Don't bury them in minor notes. - **Tiny snippet / quick question?** Keep the structure but compress it — 3 short paragraphs is fine. - **Architecture review (no diff)?** Same structure applies — "blockers" become design risks.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · freema/ai-skills | 100 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 099a1d4cb0a5 (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
- 1004r-code-review
Prowadzi ustrukturyzowany przegląd kodu wg ram 4R: ryzyko, czytelność, niezawodność i odporność. - 100pr-review
Przegląda PR i diff pod kątem zakresu, blokerów, drobnych uwag i mocnych stron, ustępując innym narzędziom recenzji, jeśli są zainstalowane. - 100code-review-checklist
Prowadzi code review według pięciu osi (poprawność, bezpieczeństwo, czytelność, wydajność, pokrycie testami) i tworzy konkretne komentarze zamiast uwag o stylu. - 91review
Przegląda istniejące pull requesty lub merge requesty z podanego linku i pomaga odpowiedzieć na uwagi w swoim PR-ze. - 90check-my-prs
Pokazuje status otwartych merge requestów: czekające na recenzję, z błędnym potokiem lub gotowe do scalenia. - 90reviews
Przegląda zmianę w kodzie lub pull request pod kątem kondycji kodu, np. na prośbę o code review.