Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

sentinel-review

Estrellas0

Forks0

Actualizado29 de abril de 2026, 07:00

Structured code review for the current diff or specified files. Flags bugs, logic errors, security issues, and style violations with severity levels. Use before committing, before PRs, or when reviewing changes.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

89jobrien

89jobrien/warpx

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

SKILL.md

readonly

name	sentinel-review
description	Structured code review for the current diff or specified files. Flags bugs, logic errors, security issues, and style violations with severity levels. Use before committing, before PRs, or when reviewing changes.

Sentinel Review

Read-only code reviewer. Flags issues, does not fix them.

Process

Identify the diff to review (staged changes, branch diff, or specified files)
Classify each finding: blocking, suggestion, or nitpick
Report all findings in a single pass
Include file path, line number, severity, and explanation for each finding

Review Categories

Correctness: logic errors, off-by-one, null/None handling
Security: injection, secrets in code, unsafe patterns
Performance: unnecessary allocations, O(n^2) where O(n) suffices
Style: naming, dead code, missing error context
Architecture: coupling, wrong abstraction layer, missing tests

Rules

Apply ALL severity levels in one pass before reporting
Do not propose fixes inline -- just flag and explain
False positives in test files (variable named password, localhost IPs) should be noted but not flagged as blocking

Más de este repositorio

mismo repositorio

writing-plans

89jobrien/warpx

Write an implementation plan as a markdown file, then immediately serialize it to a timestamped YAML task file in .ctx/tasks/. Use before touching any code when given a spec or approved design.

2026-05-030

godmode-brainstorm

89jobrien/warpx

Design-first workflow for new features, components, or architecture decisions. Use before writing any code — get explicit approval on a design first.

2026-05-030

godmode-cap

89jobrien/warpx

Commit-and-push workflow with validation. Use when asked to "cap", "commit and push", or "ship it".

2026-05-030

godmode-debug

89jobrien/warpx

Systematic debugging for Rust. Use before proposing any fix — establish root cause first, then write a failing test, then fix.

2026-05-030

godmode-parallel

89jobrien/warpx

Dispatch parallel subagents for independent tasks. Use when 2+ tasks have no shared state or sequential dependencies.

2026-05-030

godmode-tasks

89jobrien/warpx

Task graph management for a session. Use to create tasks, track progress, execute the next unblocked task, or manage dependencies between work items.

2026-05-030

name	sentinel-review
description	Structured code review for the current diff or specified files. Flags bugs, logic errors, security issues, and style violations with severity levels. Use before committing, before PRs, or when reviewing changes.

Sentinel Review

Read-only code reviewer. Flags issues, does not fix them.

Process

Identify the diff to review (staged changes, branch diff, or specified files)
Classify each finding: blocking, suggestion, or nitpick
Report all findings in a single pass
Include file path, line number, severity, and explanation for each finding

Review Categories

Correctness: logic errors, off-by-one, null/None handling
Security: injection, secrets in code, unsafe patterns
Performance: unnecessary allocations, O(n^2) where O(n) suffices
Style: naming, dead code, missing error context
Architecture: coupling, wrong abstraction layer, missing tests

Rules

Apply ALL severity levels in one pass before reporting
Do not propose fixes inline -- just flag and explain
False positives in test files (variable named password, localhost IPs) should be noted but not flagged as blocking