code-review-crsp

Review code changes for correctness, security, and requirement alignment.

3|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dvy1987/agent-loom --skill code-review-crsp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-crsp
Source: https://github.com/dvy1987/agent-loom/tree/main/.agents/skills/code-review-crsp
Command: npx skills add https://github.com/dvy1987/agent-loom --skill code-review-crsp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill produces rigorous, evidence-based code reviews that identify correctness, completeness, security, and quality issues in code changes so teams can merge with confidence and reduce regressions.

Core Features & Use Cases

  • Scope detection: Determine whether to review uncommitted changes, staged changes, branch diffs, specific files, or a PR and ask one clarifying question if the scope is ambiguous.
  • Evidence-based findings: Read diffs and surrounding context, cite file paths and exact line ranges for every issue, and classify each finding by severity (critical/high/medium/low).
  • Validation and workflow: Separate objective bugs from subjective suggestions, evaluate tests and PRD alignment, offer to apply fixes one at a time, and verify compilation and test results when available.
  • Use Case: Run a pre-merge review on a feature branch to ensure changes implement the spec, include necessary tests, and do not introduce security or performance regressions.

Quick Start

Review the current branch diff and produce a numbered, severity-classified report that cites file paths and line numbers for every issue found.

Frequently Asked Questions about code-review-crsp

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

FAQPage Schema
How do I run a security audit and bug-finding review on a pull request?

Run a pull request review to analyze branch diffs for correctness, completeness, and security vulnerabilities. The review cites exact file paths and line numbers, classifying each bug by severity and separating objective issues from subjective suggestions.

What is the best way to review uncommitted or staged changes for code quality?

Review staged or uncommitted changes to detect correctness and quality issues before merging. The process automatically determines the scope of your diff, asks one clarifying question if ambiguous, and produces a severity-classified report with cited line ranges.

How do I check if my implementation aligns with project specifications and includes necessary tests?

Evaluate PR alignment with specifications by reading the diff and surrounding context to verify implementation completeness and test coverage. The review identifies missing tests and checks whether the code fulfills the project requirements.

Can I automatically fix issues found during a diff review one at a time?

Yes, after a diff review identifies issues, you can apply fixes one at a time. The workflow verifies compilation and test results when applicable after each fix is applied to the branch.

Does the code review process separate objective bugs from subjective code quality suggestions?

The code review process explicitly separates objective bugs from subjective suggestions. Objective bugs are classified by severity as critical, high, medium, or low, ensuring actionable items are prioritized over stylistic preferences.

When do I need a formal code review for my feature branch?

You need a formal code review for a feature branch before merging to ensure changes implement the spec, include necessary tests, and do not introduce security or performance regressions into the main codebase.