agentsclimarketplace
Sign in

Review change

Skill jsuvic/agent-profile/fixtures/tabnine-workflow-skills/expected/.agents/skills/review-change

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

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.

2 things to look at

  • 3 stars3 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.
  • runs commandsInstructs the agent to run 4 commands, including `run `security-review`` and 3 more.

SKILL.md

2.1 KB, 402 tokens by cl100k_base, as published. Nobody here has run it

<!-- Generated by Agent Profile Compiler. Do not edit by hand. -->

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.