agentsclimarketplace

Code review

Skill emaraschio/cursor-commands/.cursor/skill-contracts/code-review

Production-grade Cursor slash commands with paired skill contracts, behavioral evals, and ship-gate CI. Install as a user plugin.

Install
npx -y skills add emaraschio/cursor-commands --skill code-review

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

  • 9 stars9 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

Thorough PR code review before approval

SKILL.md

2.6 KB, as published. Nobody here has run it

Overview

Perform a thorough code review that verifies functionality, maintainability, and security before approving a change. Focus on architecture, readability, performance implications, and provide actionable suggestions for improvement.

Steps

  1. Understand the change
    • Read the PR description and related issues for context
    • Identify the scope of files and features impacted
    • Note any assumptions or questions to clarify with the author
  2. Validate functionality
    • Confirm the code delivers the intended behavior
    • Exercise edge cases or guard conditions mentally or by running locally
    • Check error handling paths and logging for clarity
  3. Assess quality
    • Ensure functions are focused, names are descriptive, and code is readable
    • Watch for duplication, dead code, or missing tests
    • Verify documentation and comments reflect the latest changes
  4. Review security and risk
    • Look for injection points, insecure defaults, or missing validation
    • Confirm secrets or credentials are not exposed
    • Evaluate performance or scalability impacts of the change

Review Checklist

Functionality

  • Intended behavior works and matches requirements
  • Edge cases handled gracefully
  • Error handling is appropriate and informative

Code Quality

  • Code structure is clear and maintainable
  • No unnecessary duplication or dead code
  • Tests/documentation updated as needed

Security & Safety

  • No obvious security vulnerabilities introduced
  • Inputs validated and outputs sanitized
  • Sensitive data handled correctly

Additional Review Notes

  • Architecture and design decisions considered
  • Performance bottlenecks or regressions assessed
  • Coding standards and best practices followed
  • Resource management, error handling, and logging reviewed
  • Suggested alternatives, additional test cases, or documentation updates captured

Provide constructive feedback with concrete examples and actionable guidance for the author.

Distinction from other commands

  • decision-audit: post-build choice autopsy (meaningful decisions, confidence, pride gate) without mutating code until revise. This skill is diff quality before approve, not a judgment ledger.

Guardrails

  • Verify security-sensitive paths and test coverage before approving a change.
  • Weigh substance over style; raise nitpicks as non-blocking, not as approval blockers.
  • Do not commit, push, merge, or run production scripts without consent; wait for an explicit request before any destructive git action.

Keep looking

Skills are one crate of 328,083. 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.