skills.rest
chijunzheng
chijunzhengCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Review code across languages for defects, standards, and technical debt.

Updated Jan 17, 2026
Search Tags:#security#maintainability#review#static-analysis#lint#code-review
One-click install
npx skills add https://github.com/chijunzheng/ShowMe --skill code-review-chijunzheng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/chijunzheng/ShowMe/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/chijunzheng/ShowMe --skill code-review-chijunzheng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides expert, deterministic code reviews to catch defects, enforce standards, and reduce technical debt across codebases.

Core Features & Use Cases

  • Automated quality gates: linting, type checks, and static analysis across pull requests.
  • Comprehensive manual review: structured critique of architecture, readability, security, and maintainability.
  • Production-readiness assessment: readiness checks for releases and merge readiness.

Quick Start

Submit the patch or repository URL to the code-review agent to initiate a full, production-grade review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a thorough code review to identify defects and technical debt?▼

A thorough code review identifies defects and surfaces technical debt by combining automated linting, type checks, and static analysis with manual inspection of architecture, readability, security, and maintainability. Submit a patch or repository URL to initiate the review.

Does automated static analysis catch maintainability and security issues in pull requests?▼

Automated static analysis enforces readability, security, and maintainability standards in pull requests by running linting and type checks. It serves as a quality gate before the comprehensive manual review evaluates architecture and structural debt.

What is the best way to assess production-readiness before a release merge?▼

Assessing production-readiness requires evaluating release readiness through comprehensive code reviews that check architecture, security, and technical debt. Automated quality gates and manual inspections enforce standards across multiple languages and stacks before merging.

Can I review code quality across multiple languages and tech stacks?▼

Code quality reviews apply to new features, refactors, and pull requests across multiple languages and stacks. The review process enforces readability, security, and maintainability standards regardless of the specific tech stack used.

Do I need automated checks before starting a manual code review?▼

Automated checks like linting, type checks, and static analysis are required before manual inspection. These automated quality gates catch initial defects and enforce standards, allowing the manual review to focus on architecture and deeper technical debt.

Related Skills

Explore More Software Engineering Skills→
CsHengCsHeng
10

language-python

Run Ruff, Mypy, and Pytest checks on Python code.

Community
Advanced
fredrikaverpilfredrikaverpil
253

code-review

Enforce evidence-based verification gates before claiming code review completion.

Community
Basic
pohlai88pohlai88

ci-cd-pipeline

Manage CI/CD pipelines, GitHub Actions workflows, and deployment strategies.

Community
Advanced
oioio-spaceoioio-space

secret-guard

Scan staged Git diffs for credentials, PII, and sensitive data.

Community
Advanced