Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

review-change

Estrelas3

Forks0

Atualizado3 de julho de 2026 às 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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

jsuvic

jsuvic/agent-profile

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Analistas de garantia de qualidade de software e testadoresInformática e Matemática·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.

Mais deste repositório

mesmo repositório

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.