skills.rest
magicpro97
magicpro97COMMUNITY
Explore all skills by this author →
GitHub

code-reviewer

Identify genuine bugs, security vulnerabilities, and logic errors in code reviews.

1|1|Updated Apr 10, 2026
Search Tags:#security#edge-cases#code-review#contracts#pull-request#bug-detection
One-click install
npx skills add https://github.com/magicpro97/copilot-session-knowledge --skill code-reviewer-magicpro97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/magicpro97/copilot-session-knowledge/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/magicpro97/copilot-session-knowledge --skill code-reviewer-magicpro97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often miss real issues. This skill focuses on surfacing only genuine bugs, security vulnerabilities, and logic errors, avoiding distraction from style or formatting.

Core Features & Use Cases

  • High-signal review targets correctness and security, not style.
  • PR & diff ready suitable for code changes, modules, and agent-produced code.
  • Guided process emphasizes contracts, invariants, and edge cases to reduce regressions.

Quick Start

Review a new or updated code submission to obtain immediate, actionable feedback on critical issues.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I find security vulnerabilities and logic errors in a pull request?▼

A high-signal code review targets correctness and security rather than style, checking contracts and invariants to surface genuine bugs. This guided process focuses on failure paths and edge cases to reduce regressions in critical modules.

What is the best way to review agent-produced code for genuine bugs?▼

Reviewing agent-produced code requires a disciplined process that checks contracts and invariants while focusing on correctness and security in critical modules. This approach avoids style distractions to surface only genuine bugs.

Can I use this code review process for diffs across any software project?▼

Yes, this code review process is suitable for code changes, modules, and agent-produced code across software projects. It focuses on high-signal detection of logic errors and security vulnerabilities in diffs and pull requests.

How do I surface edge cases and check invariants during a code review?▼

To surface edge cases and check invariants during a code review, apply a guided process that enforces a disciplined review of failure paths. This targets correctness and security to ensure only genuine bugs are surfaced.

Why does my code review miss real security vulnerabilities and logic errors?▼

Code reviews often miss real security vulnerabilities and logic errors when they focus on style or formatting rather than correctness. A high-signal review targets genuine bugs by checking contracts and emphasizing edge cases.

Related Skills

Explore More Software Engineering Skills→
cryptopaficryptopafi

github-code-review

Review git diffs and GitHub pull requests with structured feedback.

Community
Intermediate
DarkArty07DarkArty07
3

requesting-code-review

Catches security vulnerabilities, logic errors, and test regressions in code changes before git commit.

Community
Advanced
zhizhunbaozhizhunbao

code-style

Configure Ruff, Prettier, ESLint, and mypy with pre-commit hooks for Python and TypeScript.

Community
Intermediate
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced