skills.rest
Nickalus12
Nickalus12COMMUNITY
Explore all skills by this author →
GitHub

review

Review code diffs and staged changes with severity-ordered findings.

2|Updated Apr 4, 2026
Search Tags:#diff#quality-assurance#code-review#severity#scopes#file-references#loom-style
One-click install
npx skills add https://github.com/Nickalus12/Loom --skill review-nickalus12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/review
Command: npx skills add https://github.com/Nickalus12/Loom --skill review-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loom-style code reviews ordered by severity with concrete file references to speed up issue triage and improve reliability.

Core Features & Use Cases

  • Severity-ranked findings with file and line references
  • Scope-aware review: explicit paths, staged changes, or last-commit diff
  • Protocol-driven delegation and maintainability guidance for PRs

Quick Start

Review the specified scope (explicit paths, staged changes, or last commit diff) and present findings ordered by severity with concrete file references.

Frequently Asked Questions about review

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

FAQPage Schema
How do I get a code review with findings ranked by severity?▼

A Loom-style code review evaluates your specified scope and presents findings ordered by severity. It includes concrete file and line references to speed up issue triage and improve reliability through actionable remediation notes.

Can I run a code review on just my staged changes or last commit diff?▼

Yes, code reviews can be performed on explicit paths, staged changes, or last-commit diffs. This scope-aware approach ensures reproducible findings with concrete file references prioritized by impact.

What is a Loom-style code review?▼

A Loom-style code review presents severity-ranked findings with concrete file and line references. It applies protocol-driven delegation and maintainability guidance to codebases with explicit paths, staged changes, or last-commit diffs.

How do I ensure code review findings are reproducible and actionable?▼

Reproducible code review findings require concrete file and line references. The review ensures reproducibility by evaluating explicit paths, staged changes, or last-commit diffs and prioritizing findings by impact with actionable remediation notes.

Does this code review approach work for pull request maintainability guidance?▼

Yes, the review provides protocol-driven delegation and maintainability guidance for PRs. It evaluates your specified scope and outputs severity-ranked findings with concrete file references to speed up issue triage.

Related Skills

Explore More Software Engineering Skills→
sorryhyunsorryhyun
12

clean-comments

Remove redundant code comments while preserving valuable explanations during code cleanup.

Community
Basic
MovchanetsMovchanets

code-review-excellence

Review pull requests with severity-ranked findings on correctness, security, performance, and maintainability.

Community
Advanced
NITISH-gitbitNITISH-gitbit

requesting-code-review

Automate pre-commit code review and security scans on git diffs.

Community
Advanced
mwathibenmwathiben

typescript-review

Review TypeScript and JavaScript diffs against Metabase coding standards.

Community
Intermediate