review-security
/review-security
Przegląda zmiany pod kątem wykorzystywalnych luk bezpieczeństwa, granic zaufania, uwierzytelniania, autoryzacji, sekretów i niebezpiecznego wejścia.
- Autor
- cbeeswax ↗
- Repozytorium
- code-review-skill ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 01.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 01.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
Przegląda zmiany pod kątem wykorzystywalnych luk bezpieczeństwa, granic zaufania, uwierzytelniania, autoryzacji, sekretów i niebezpiecznego wejścia.
Oryginalny opis (EN)
Review code changes for exploitable security vulnerabilities, trust boundary violations, authentication, authorization, secrets, and unsafe input handling. Use for /review-security.
Jak działa
- Focus
- Evidence contract
- Finding rules
- Inline comment style
- Pull-request behavior
Podgląd SKILL.md
--- name: review-security description: Review code changes for exploitable security vulnerabilities, trust boundary violations, authentication, authorization, secrets, and unsafe input handling. Use for /review-security. license: MIT --- # review-security ## Focus Treat security as an independent review. Trace untrusted input to sensitive sinks and verify authentication, authorization, tenancy, cryptography, secret handling, deserialization, command execution, file access, and network boundaries affected by the change. Every security finding needs an attack path, affected asset or boundary, and reproducible evidence or a traced exploit chain. Do not dilute security findings with style feedback. Escalate missing trust-boundary evidence as an explicit review gap. ## Evidence contract Review the change's stated intent, affected boundary, and non-negotiable constraints before judging implementation details. Build an evidence ledger: 1. **Intent and constraints:** What behavior is changing? What must remain true? What is explicitly out of scope? 2. **Evidence collected:** Commands, tests, simulations, traces, benchmarks, screenshots, or repository contracts actually inspected or run. 3. **Result:** What each source of evidence proves, disproves, or does not cover. 4. **Evidence gaps:** Important behavior that cannot be verified from the available code, tests, tooling, or stated intent. 5. **Residual risk and rollback:** What may still fail, how it will be detected, and how the change can be safely reversed. Rank evidence in this order: 1. Reproducible test, simulation, benchmark, screenshot, command output, or observed failing behavior. 2. A traced code path tied to a documented contract, invariant, or established repository behavior. 3. Inference from a diff, name, or pattern alone. Only the first two levels support a defect finding. Treat level-three concerns as evidence gaps or questions, never as asserted bugs. ## Finding rules Report only issues introduced or made reachable by the reviewed change. Mark pre-existing issues separately. Do not report style preferences, speculative problems, or cleanup unless they create a concrete correctness, security, privacy, reliability, or performance impact. Each finding must include: - Severity and confidence. - Business context first: the affected customer, operational outcome, revenue, compliance, trust, or delivery risk. - A concrete failure scenario in plain language. - Changed file and line evidence, then the technical cause in only the detail needed to make the remediation clear. - A specific remediation or verification step. - Introduced versus pre-existing classification. - Test or validation evidence. Start the final report with the count of verified findings. If there are none, say `0 verified findings` plainly. Include evidence gaps separately. ## Inline comment style Write inline comments for a business reader before a technical reader. Lead with what could go wrong, for whom, and under what condition. Follow with the minimum code-level evidence needed to make the concern credible and actionable. Avoid unexplained framework names, implementation trivia, or jargon in the first sentence. Use this shape: ```text [Severity] Business consequence When <business scenario>, <customer, operational, financial, compliance, or trust consequence> can occur. This change <plain-language explanation of why>. Evidence: <file:line and concise technical cause> Suggested next step: <specific fix or verification> ``` For example, write `A customer could be charged twice after a payment timeout` instead of `Missing idempotency guard in retry path`. Keep the technical cause in the evidence line. Do not post a comment if the business consequence cannot be explained from the available evidence. ## Pull-request behavior Produce a local report by default. Post GitHub comments only when the user explicitly asks and the available integration supports it. Post only high-confidence, evidence-backed, actionable findings inline and one concise business-impact summary. Keep broad process notes, evidence gaps, and low-confidence concerns in the local report rather than posting them inline. Never post hypotheses, approve a pull request, merge, or modify code unless the user explicitly requests that separate action.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · cbeeswax/code-review-skill | 100 | MIT |
| borkweb/bork-ai | 100 | MIT |
| tojim00d/Orbit-skills | 100 | MIT |
| yuri-xyz/skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki ba4d0826e9fd (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
- 96security-review
Przegląda kod i zmiany pod kątem podatności: wstrzyknięć, sekretów, niebezpiecznego wejścia i uprawnień. - 100security-review
Ocenia kod i konfigurację pod kątem ryzyka dla wrażliwych danych, granic zaufania, uwierzytelniania, uprawnień, wejścia, sekretów i zależności. - 100secure-code-review
Przegląda zmianę w kodzie pod kątem błędów bezpieczeństwa, które można wykorzystać, z uwzględnieniem granic zaufania i przepływu danych. - 100security-review
Przegląda zmiany w kodzie pod kątem podatności aplikacyjnych, w tym uwierzytelniania, autoryzacji, wycieków sekretów i ekspozycji danych wrażliwych, w stylu przeglądów OWASP. - 90security-review
Przegląda zmiany pod kątem luk OWASP, uwierzytelniania i autoryzacji oraz wrażliwych miejsc, gdy pojawia się prośba o przegląd. - 100nobrainer-security
Przeprowadza model zagrożeń i przegląd bezpieczeństwa zmian dotykających uwierzytelniania, autoryzacji, sekretów, niezaufanych danych, wrażliwych danych, zależności i granic zaufania produkcji.