Review change

Skill jsuvic/agent-profile/fixtures/advanced-review-enabled/expected/.claude/skills/review-change

Configure Codex, Claude, and Tabnine to understand your project, follow its workflow, and respect its safety rules.

Install

npx -y skills add jsuvic/agent-profile --skill review-change

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.1 KB, as published. Nobody here has run it

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.