skills.rest
KYRIE66nb
KYRIE66nbCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-review

Review code changes for security vulnerabilities, quality issues, and maintainability concerns.

Updated Apr 8, 2026
Search Tags:#git#security#maintainability#quality#code-review#pull-request
One-click install
npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill code-review-kyrie66nb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/KYRIE66nb/codex-omx-public-config/tree/main/home/.agents/skills/code-review
Command: npx skills add https://github.com/KYRIE66nb/codex-omx-public-config --skill code-review-kyrie66nb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review processes often miss subtle defects, security vulnerabilities, and maintainability concerns in rapidly changing codebases. This skill provides a structured, repeatable review that surfaces high-risk issues before merges.

Core Features & Use Cases

  • Security: Detects hardcoded secrets, insecure patterns, and potential attack vectors.
  • Code Quality: Measures complexity, duplication, and readability.
  • Maintainability: Highlights architectural smells, testability gaps, and documentation needs.
  • Use Case: Before merging a PR, generate a focused report that guides developers to fix critical issues and improve code health.

Quick Start

Provide the code changes (git diff) or the PR link to initiate a thorough review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a git diff for security vulnerabilities before a pull request merge?▼

Reviewing a pull request for maintainability involves analyzing architectural smells, testability gaps, and documentation needs. The review highlights complexity and duplication issues, providing an auditable output that guides developers to improve code health and structural readability before merging.

Can I use automated code review across different programming languages and frameworks?▼

Automated code review can be applied across different programming languages and frameworks. It processes provided feature branches and diffs to identify quality issues and security concerns, delivering concrete fix recommendations and an auditable review output regardless of the specific tech stack.

What is the best way to categorize code quality issues by severity in a pull request?▼

The best way to categorize code quality issues by severity in a pull request is to generate a focused review report. This report localizes findings to specific files and lines, categorizing security vulnerabilities and maintainability concerns by their risk level to guide developers toward critical fixes.

Does code review work without configuring external dependencies or components?▼

Code review works without configuring external dependencies or components. You simply provide the code changes or pull request link directly, and the review mechanism surfaces high-risk issues, architectural smells, and security vulnerabilities in an auditable output.

Related Skills

Explore More Software Engineering Skills→
a-taka-tak
1

git-create-pr

Commit changes, push to origin, and create a GitHub Pull Request.

Community
Intermediate
adilkalamadilkalam
2

linter-loop-limits

Enforce a three-strike cap on iterative linter-fix loops.

Community
Basic
prof-danielcprof-danielc

speckit.checker

Run static analysis tools and aggregate results into a prioritized issue report.

Community
Advanced
hospitaljobsinhospitaljobsin
7

code-review-excellence

Structure code reviews with checklists and feedback templates.

Official
Intermediate