skills.rest
saranskumar
saranskumarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-reviewer

Review code changes for correctness, security-sensitive logic, and boundary violations.

Updated Apr 19, 2026
Search Tags:#testing#security#maintainability#code-review#risk-analysis#regressions
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill code-reviewer-saranskumar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/saranskumar/anti-slop/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/saranskumar/anti-slop --skill code-reviewer-saranskumar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews can miss critical risks like security issues, boundary violations, and regressions. This Skill guides reviewers to focus on correctness, trust boundaries, and maintainability, helping teams catch issues before merging.

Core Features & Use Cases

  • Review for correctness, trust boundaries, and boundary separation.
  • Identify likely regressions, missing validations, and risky duplication.
  • Prioritize findings by severity and likelihood.
  • Note missing tests or rollout risks.

Quick Start

Provide a production-minded review of the given change set focusing on risks and boundary issues.

Frequently Asked Questions about code-reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a code review to uncover security risks and regressions?▼

Identify likely regressions and missing validations in a code review by checking boundary separation, prioritizing findings by severity and likelihood, and noting missing tests or rollout risks across changed files.

How do I identify missing tests and rollout risks in a multi-file PR?▼

Identify missing tests and rollout risks in a pull request by assessing configuration changes across multiple layers, enforcing structured risk prioritization, and communicating actionable findings regarding trust boundaries.

What is the best way to review code changes for correctness and maintainability?▼

The best way to review code changes for correctness and maintainability is to guide the review process to focus on trust boundaries, identify risky duplication, and prioritize actionable findings by severity.

Can I use a code review process for config changes that require risk assessment?▼

Yes, a production-grade code review process applies to config changes requiring risk assessment by evaluating security-sensitive logic, identifying boundary violations, and communicating actionable findings prioritized by severity.

When do I need structured risk prioritization during code reviews?▼

You need structured risk prioritization during code reviews when evaluating pull requests spanning multiple files or layers, feature areas, or config changes to accurately assess correctness, trust boundaries, and rollout risks.

Related Skills

Explore More Software Engineering Skills→
anukkrit149anukkrit149

gitnexus-pr-review

Detect code changes in pull requests and map them to affected execution flows and symbols.

Community
Advanced
mczkzkmczkzk

pr-review

Review GitHub pull requests and diffs for bugs, regressions, security risks, and missing tests.

Community
Advanced
sjinkssjinks

security-review-owasp-kubernetes-security

Review Kubernetes security controls for unsafe defaults and privilege sprawl.

Community
Advanced
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate