development-code-review

Automate structured local code reviews with risk scoring and actionable findings.

26|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/TeamSloppy/Sloppy --skill development-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: development-code-review
Source: https://github.com/TeamSloppy/Sloppy/tree/main/Sources/sloppy/Resources/Skills/development-code-review
Command: npx skills add https://github.com/TeamSloppy/Sloppy --skill development-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers perform thorough, structured code reviews locally or in non-GitHub contexts, focusing on correctness, maintainability, security, tests, and release risk.

Core Features & Use Cases

  • Diff-first evaluation: Analyze the change set to identify correctness issues, maintainability concerns, and potential security risks.
  • Context-aware inspection: Review full file context, tests, and surrounding code to understand implications of changes.
  • Actionable findings: Produce structured, file-and-line referenced feedback with concrete remediation steps and risk scoring.
  • Workflow guidance: When GitHub PR comments or approvals are required, route to github-code-review to perform PR-level tasks.
  • Comprehensive checklist: Use a formal checklist covering Correctness, Security and Privacy, Maintainability, Testing, Performance and Reliability, and Documentation and UX.

Quick Start

Provide a local code review by first inspecting the diff, then validating tests, security, and maintainability, and returning structured findings.

Frequently Asked Questions about development-code-review

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

FAQPage Schema
How do I perform a structured local code review on a diff?

Perform a structured local code review by analyzing the diff first, then validating full-file context, tests, and maintainability to return actionable findings with file references and risk scores.

What is diff-first analysis in pre-merge code assessments?

Diff-first analysis evaluates the change set to identify correctness issues, maintainability concerns, and potential security risks before validating the surrounding full-file context.

Can I use this for non-GitHub code review scenarios?

Yes, you can use this for non-GitHub code review scenarios to execute local reviews, though GitHub PR comments and API approval actions require routing to github-code-review.

What does a formal code review checklist cover for maintainability and security?

A formal code review checklist covers Correctness, Security and Privacy, Maintainability, Testing, Performance and Reliability, and Documentation and UX to ensure comprehensive software quality assurance.

How do I score release risk for multi-file code changes?

Score release risk for multi-file changes by inspecting edge cases and full-file context during the review, producing structured findings that include concrete remediation steps and risk metrics.