code-review

Evaluate code changes against security and quality review checklists.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/helix4u/hermes-agent --skill code-review-helix4u
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/helix4u/hermes-agent/tree/main/skills/software-development/code-review
Command: npx skills add https://github.com/helix4u/hermes-agent --skill code-review-helix4u

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Code Review Skill provides a structured, security- and quality-focused framework for evaluating code changes, helping teams catch defects early and improve maintainability.

Core Features & Use Cases

  • Security-first checks such as input validation, secret handling, and access controls.
  • Error handling and reliability reviews, readability, and adherence to style guides.
  • Review responses and standardized feedback to accelerate merge decisions and knowledge transfer.
  • Use Case: Apply this skill when reviewing a PR to verify that dependencies are safe, sensitive data is protected, and potential edge cases are covered.

Quick Start

Review an incoming pull request against the checklist to identify security and quality issues and provide actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate security and quality checks for a pull request?▼

You can automate code review for a pull request by applying a checklist-driven evaluation that enforces security, error handling, and readability criteria to generate standardized actionable feedback.

What is a structured code review framework for identifying hardening and readability improvements?▼

A structured code review framework applies explicit security and quality checklists to changesets, focusing on identifying input validation flaws, access control gaps, and style guide violations across languages.

Can I use static analysis guidelines to audit code changes across different repositories?▼

Yes, you can apply these static analysis guidelines to audit code changes across multiple languages and repositories by enforcing standardized criteria for sensitive data protection and edge case coverage.

What's the best way to standardize pull request feedback for security and quality issues?▼

The best way to standardize pull request feedback is to enforce a standardized review response format that requires explicit criteria for security, error handling, and testing considerations during code changeset evaluation.

Does checklist-driven code review work for changesets across multiple programming languages?▼

Yes, checklist-driven code review works for changesets across multiple programming languages by applying universal best-practice guidelines for security, reliability, and adherence to style guides.

When should I not rely on automated code review for merge decisions?▼

You should not rely solely on automated code review when evaluating complex business logic or architectural changes, as the checklist-driven approach focuses primarily on security hardening, error handling, and readability improvements.