Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

review-change

Estrellas3

Forks0

Actualizado3 de julio de 2026 a las 17:52

Use to review a proposed change for correctness, security-sensitive behavior, readability, tests, performance when relevant, architecture and contract impact, and generated-file drift.

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

jsuvic

jsuvic/agent-profile

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	review-change
description	Use to review a proposed change for correctness, security-sensitive behavior, readability, tests, performance when relevant, architecture and contract impact, and generated-file drift.

Review Change

Use these rules when reviewing a pull request or proposed change.

Review Focus

Correctness and edge cases.
Security, including input validation and secret handling.
Performance hotspots and obvious complexity regressions.
Unnecessary complexity or premature abstraction.
Consistency with existing project style.
Missing or weakened tests.
Weak typing or unjustified any.
Accessibility-affecting behavior in user-facing changes.
Error handling and observability gaps.
Dependency risk and license concerns.
Spec compliance.

Severity Labels

Blocker: must fix before merge (correctness, security, contract break).
High: must fix before merge unless explicitly deferred.
Medium: should fix before merge or open a tracked follow-up.
Low: nit or polish; safe to defer.

Output Format

Summary: one paragraph of intent and overall verdict.
Spec Compliance: cite the spec and any deviation.
Findings: grouped by severity, each with file, function, and concrete suggestion.
Tests: list coverage gaps and whether tests were run.
Safety Review: secrets, production access, dependency installs, network access.
Final recommendation: approve, request changes, or block with reason.

Review Discipline

Skip nitpicks the autoformatter or linter already handles.
Do not propose broad rewrites; keep suggestions actionable.
Reference the specific file, function, or component in every finding.

Specialist Reviews

For a deeper pass, run security-review.
For a deeper pass, run readability-review.
For a deeper pass, run test-review.
For a deeper pass, run architecture-review.

Safety

Review only; do not rewrite or apply patches unless the user asks.
Do not upload source code or read or print secrets.
Do not install dependencies, contact production systems, or broaden permissions.

Más de este repositorio

mismo repositorio

grill-change

jsuvic/agent-profile

Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.

2026-07-133

request-to-spec-issues

jsuvic/agent-profile

Use after a grill-change session is complete to turn the agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs.

2026-07-133

grill-change

jsuvic/agent-profile

Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.

2026-07-133

request-to-spec-issues

jsuvic/agent-profile

Use after a grill-change session is complete to turn the agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs.

2026-07-133

loop-security-patch-retest

jsuvic/agent-profile

Use to run a bounded security-review, patch, and retest loop that stops on green, on no diff, or on a repeated identical finding.

2026-07-113

final-review

jsuvic/agent-profile

Use before handing off an implementation to compare the diff against the spec, tests, docs, contracts, and safety rules.

2026-07-063

Review Change

Use these rules when reviewing a pull request or proposed change.

Review Focus

Correctness and edge cases.

Security, including input validation and secret handling.

Performance hotspots and obvious complexity regressions.

Unnecessary complexity or premature abstraction.

Consistency with existing project style.

Missing or weakened tests.

Weak typing or unjustified any.

Accessibility-affecting behavior in user-facing changes.

Error handling and observability gaps.

Dependency risk and license concerns.

Spec compliance.

Severity Labels

Blocker: must fix before merge (correctness, security, contract break).

High: must fix before merge unless explicitly deferred.

Medium: should fix before merge or open a tracked follow-up.

Low: nit or polish; safe to defer.

Output Format

Summary: one paragraph of intent and overall verdict.

Spec Compliance: cite the spec and any deviation.

Findings: grouped by severity, each with file, function, and concrete suggestion.

Tests: list coverage gaps and whether tests were run.

Safety Review: secrets, production access, dependency installs, network access.

Final recommendation: approve, request changes, or block with reason.

Review Discipline

Skip nitpicks the autoformatter or linter already handles.

Do not propose broad rewrites; keep suggestions actionable.

Reference the specific file, function, or component in every finding.

Specialist Reviews

For a deeper pass, run security-review.

For a deeper pass, run readability-review.

For a deeper pass, run test-review.

For a deeper pass, run architecture-review.

Safety

Review only; do not rewrite or apply patches unless the user asks.

Do not upload source code or read or print secrets.

Do not install dependencies, contact production systems, or broaden permissions.