code-reviewer

Analyze codebases for defects, security issues, and quality regressions with PASS or FAIL outcomes.

6|3|Updated Mar 26, 2026

Search Tags:#code review #workflow automation #rollback #security audit #quality gates #bilingual #cwe scanning

Ready to run

npx skills add https://github.com/theneoai/skill-writer --skill code-reviewer-theneoai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/theneoai/skill-writer/tree/main/examples/code-reviewer
Command: npx skills add https://github.com/theneoai/skill-writer --skill code-reviewer-theneoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams review code consistently by catching defects, security issues, and quality regressions before changes are merged.

Core Features & Use Cases

Multi-step code review: Guides a structured review flow with validation, static analysis, pattern detection, quality gates, and report generation.
Security-focused auditing: Checks for common risks such as hardcoded credentials, SQL injection, command injection, and path traversal.
Bilingual support: Handles English and Chinese review requests while keeping security references and findings consistent.
Rollback-aware workflow: Stops and recovers cleanly when thresholds fail, helping reviewers act on issues without losing process control.

Quick Start

Use the code-reviewer skill to review the attached codebase for security issues, quality problems, and actionable improvements.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema

How do I automate code review for security issues in pull requests?▼

Automated code review identifies security issues in pull requests by applying static analysis, pattern detection, and quality gates. It evaluates source files for hardcoded credentials, SQL injection, and command injection, generating explicit PASS or FAIL outcomes based on severity.

How does CWE scanning work during a security audit?▼

CWE scanning works by mapping detected vulnerabilities to common weakness enumerations during a security audit. It analyzes source files for path traversal and command injection risks, generating severity-aware reports that flag specific security flaws before generating a final PASS or FAIL outcome.

Can I review code written in Chinese and English?▼

You can review code using bilingual requests in both Chinese and English. The workflow processes review instructions in both languages while maintaining consistent security references, CWE mappings, and defect reporting across the generated outputs.

What happens when quality gates fail during a code review workflow?▼

When quality gates fail during a code review workflow, the process stops and triggers a rollback-aware recovery. This prevents merging changes by halting the review cleanly, allowing reviewers to act on severity-aware defects without losing process control.

What is the best way to prevent quality regressions before merging code?▼

Preventing quality regressions requires applying structured quality gates and static analysis to pull requests. By enforcing severity-aware reporting and rollback handling, the workflow detects defects and security issues early, ensuring only validated changes pass the final review.