code-review-checklist
Review Code with a Five-Axis Checklist
Unstructured code reviews can miss defects and spend time on style preferences. This skill guides five review areas and produces prioritized comments with concrete fixes.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "code-review-checklist" from https://skillstore.io/skills/alapha888-code-review-checklist.md and its manifest at https://skillstore.io/api/skills/alapha888-code-review-checklist/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "code-review-checklist". A small order-processing diff indexes the first order without checking whether the list is empty.
Resultado esperado:
- Must fix | Correctness | order.py:87: An empty order list causes IndexError. Check for an empty list before accessing its first item.
- Should fix | Test coverage | order.py:87: Add an empty-order test to cover the failing path.
Usando "code-review-checklist". A contributor requests review of a diff containing 650 changed lines.
Resultado esperado:
Scope: The diff exceeds approximately 400 changed lines. Split it into smaller, focused changes before review.
Usando "code-review-checklist". A reviewer suspects a loop is slow but provides no measurements or evidence of repeated work.
Resultado esperado:
Performance: No evidence found to support a performance finding. Do not raise a speculative performance comment.
Auditoría de seguridad
SeguroAll six static findings are false positives: Markdown formatting was mistaken for command execution, and ordinary review prose was mistaken for reconnaissance. No evidence found of prompt injection, credential access, or data exfiltration in SKILL.md. The skill contains review guidance and examples, not executable tooling.
Factores de riesgo
⚙️ Comandos externos (5)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/alapha888-code-review-checklist/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/alapha888-code-review-checklist?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/alapha888-code-review-checklist?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alapha888-code-review-checklist/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/alapha888-code-review-checklist.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
alapha888. (2026). code-review-checklist security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alapha888-code-review-checklist/audits/1Cita BibTeX
@techreport{alapha888-alapha888-code-review-checklist-2026,
author = {alapha888},
title = {code-review-checklist security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/alapha888-code-review-checklist/audits/1},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "code-review-checklist security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "alapha888"
date-released: "2026-10-06"
url: "https://skillstore.io/skills/alapha888-code-review-checklist/audits/1"
identifiers:
- type: other
value: "skillstore:alapha888-code-review-checklist:audit:1"
description: "Skillstore immutable audit report identifier"
Comparar variantes
2 variantes instalablesCada autor sigue siendo un skill instalable independiente. La variante recomendada se ordena según la evidencia de Skillstore.
Por qué esta variante es la primera
sickn33-code-review-checklist
2026-09-09
alapha888-code-review-checklist
2026-10-11
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Check a change before submission
Review a small diff for edge cases, security risks, and missing tests before opening a pull request.
Standardize team review comments
Apply consistent review categories and priorities while keeping feedback tied to specific lines and concrete fixes.
Evaluate unfamiliar contributions
Review community changes for correctness, readability, and test coverage without focusing on formatting preferences.
Prueba estos prompts
Review this function using the five-axis checklist: [paste function with file name and line numbers]. Cite specific lines and suggest concrete fixes.
Review this diff: [paste diff]. Check scope first, then all five axes. Separate Must fix and Should fix comments. Use at most ten comments.
Review this authentication change: [paste diff and requirements]. Check correctness, injection risks, secrets, logging, and remaining axes. Cite evidence and identify missing edge-case tests.
Review this diff with requirements, tests, and profiling results: [attach context]. Mark each axis pass, fail, or N-A. Prioritize concrete fixes within ten comments.
Mejores prácticas
- Provide the diff, file names, line numbers, and relevant requirements.
- Split changes over approximately 400 lines into focused reviews.
- Require evidence and a concrete fix for each comment, and clarify team merge-blocking rules.
Evitar
- Approve a change without reading the complete diff.
- Spend review comments on formatting preferences instead of substantive defects.
- Report vague problems or performance concerns without code references and evidence.