skills.rest
locnbk2002
locnbk2002COMMUNITY
Explore all skills by this author →
GitHub

code-review

Orchestrate a scout-review-fix pipeline with severity classification for code changes.

1|Updated Feb 28, 2026
Search Tags:#code review#pull request#security#quality gate#pre-commit#bug detection
One-click install
npx skills add https://github.com/locnbk2002/my-copilot --skill code-review-locnbk2002
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/locnbk2002/my-copilot/tree/main/my-copilot/skills/code-review
Command: npx skills add https://github.com/locnbk2002/my-copilot --skill code-review-locnbk2002

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates and structures the code review process, ensuring code quality, security, and adherence to project standards before merging.

Core Features & Use Cases

  • Structured Review Pipeline: Orchestrates a scout-review-fix workflow.
  • Severity Classification: Categorizes issues into Critical, High, Medium, and Low.
  • Strict Enforcement: Optionally enforces fixing of critical and high-severity issues.
  • Use Case: Integrate into your CI/CD pipeline as a quality gate, or use it locally before committing code to catch potential bugs and security vulnerabilities.

Quick Start

Run a code review on your staged changes.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate pull request reviews before merging code?▼

Automate pull request reviews by orchestrating a structured scout-review-fix pipeline that categorizes code changes by severity. This enforces quality gates and pre-commit checks to catch bugs and security vulnerabilities before merging.

What is the scout-review-fix pipeline for code changes?▼

The scout-review-fix pipeline is a structured code review workflow that identifies, evaluates, and corrects code changes. It categorizes discovered issues into Critical, High, Medium, and Low severity levels for targeted resolution.

Do I need git to run a pre-commit code review?▼

Yes, you need git to run this pre-commit code review because the process requires git for diffing code changes. An agent is also required to perform the actual review and severity classification.

Can I enforce fixing critical bugs as a CI/CD quality gate?▼

Yes, you can enforce fixing critical and high-severity bugs as a CI/CD quality gate. The review process optionally mandates resolution of these top-tier issues before allowing code changes to proceed.

How are security vulnerabilities classified during code reviews?▼

Security vulnerabilities and bugs are classified during code reviews using a severity categorization system. Issues are sorted into Critical, High, Medium, and Low levels to prioritize fixes and enforce strict quality gates.

Related Skills

Explore More Software Engineering Skills→
StarryCodStarryCod
11

requesting-code-review

Run static security scans, tests, linting, and independent review on staged git changes.

Community
Advanced
oxieoxie

staging-deployment-phase

Automate staging deployment with auto-merge for merged pull requests.

Community
Intermediate
winsorllcwinsorllc

code-review

Execute linters, static analysis, and security scanners on code.

Community
Intermediate
DarkMonkDevDarkMonkDev
1

test-environment

Run unit, integration, and end-to-end tests in isolated containers.

Community
Advanced