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

code-review

Review code with severity-based reporting and scope-detection rules.

2|Updated Apr 4, 2026
Search Tags:#automation#security#review#ci-cd#code-review#quality-gates#defect-detection
One-click install
npx skills add https://github.com/Nickalus12/Loom --skill code-review-nickalus12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/code-review
Command: npx skills add https://github.com/Nickalus12/Loom --skill code-review-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standalone code review methodology that enables structured, severity-classified assessment, reducing ambiguity and ensuring consistent quality gates across projects.

Core Features & Use Cases

  • Scope-detection protocol prioritizes user-provided paths, staged changes, and last-commit diffs to determine review scope
  • Delegation to a code-reviewer agent with full diff content, contextual file contents, and user concerns
  • Clear severity taxonomy (Critical, Major, Minor) and a structured output format for reports and quality gates

Quick Start

Provide the initial scope (file paths or patterns) or rely on the built-in scope-detection pipeline to determine changes and begin the review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate structured code reviews for CI-CD quality gates?▼

Automated code reviews enforce deterministic, severity-based reporting to act as quality gates. This process applies a scope-detection protocol prioritizing user paths, staged changes, and last-commit diffs to ensure consistent quality gates across projects.

What is the best way to detect the scope of staged changes for a code review?▼

Scope detection for a code review prioritizes user-provided file paths first. If absent, it checks staged changes, then last-commit diffs, and finally prompts the user for scope, ensuring comprehensive coverage of relevant modifications.

How does severity-based defect detection work in automated code reviews?▼

Severity-based defect detection in code reviews uses a clear taxonomy of Critical, Major, and Minor classifications. This structured format provides reproducible output for reports, reducing ambiguity and ensuring consistent quality gates across projects.

Can I perform secure code reviews at scale without specifying file paths?▼

Yes, secure code reviews at scale can run without explicit paths by using a built-in scope-detection pipeline. The system automatically evaluates staged changes and last-commit diffs, only prompting for scope if no changes are detected.

How do I standardize code review output for security and defect detection across projects?▼

Standardizing code review output requires a reproducible report format using a severity-based taxonomy. This methodology delegates reviews to an agent with full diff content and contextual files, ensuring consistent, structured quality gates.

Related Skills

Explore More Software Engineering Skills→
jossteijosstei
453

code-review

Automate code reviews with scope detection and structured severity reporting.

Community
Advanced
tygwantygwan
1

quality-gate

Automate quality validation at pre-commit, pre-merge, pre-release, and post-release CI gates.

Community
Advanced
sobhanashinesobhanashine
1

ship

Automate software deployment by merging branches, running tests, and updating versioning.

Community
Advanced
guma154-cmdguma154-cmd

coderabbit-review

Automate CodeRabbit CLI code reviews in WSL environments.

Community
Intermediate