code-review

Identify security and quality gaps in code changes during reviews.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured framework for conducting rigorous code reviews focused on security, quality, and maintainability, ensuring issues are identified and communicated consistently.

Core Features & Use Cases

  • Security-first checks to catch hardcoded secrets, insecure input handling, weak authentication/authorization, and insecure configurations.
  • Error handling and resilience checks, including proper logging, clear error messages, and resource cleanup.
  • Code quality criteria that promote readability, modularity, DRY principles, descriptive naming, and avoidance of dead code.
  • Testing considerations that ensure coverage of edge cases, happy paths, and meaningful test feedback during reviews.
  • Standardized feedback formats and templates to guide reviewers and maintainers in consistent communication.

Quick Start

Review a pull request by applying the checklist to assess security, reliability, and maintainability, then provide actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema
What should a code review checklist include for security and quality?

A code review checklist should include security-first checks for hardcoded secrets and insecure input handling, alongside quality criteria like readability, modularity, DRY principles, and meaningful test coverage to ensure maintainability.

How do I review a pull request for security vulnerabilities and error handling?

Review a pull request by applying a structured checklist to assess security gaps like weak authentication, verify proper logging and error messages, and confirm resource cleanup to ensure resilience and safe coding practices.

How do I write standardized feedback for code review maintainers?

Write standardized feedback for code review maintainers by using structured templates that guide consistent communication, specify functional and technical requirements, and provide actionable feedback on identified security and quality gaps.

Does this code review framework apply across multiple programming languages?

Yes, this code review framework applies to pull requests and code audits across multiple programming languages, focusing on language-agnostic security-first checks, error handling, maintainability, and safe coding guidance.

What is the best way to audit code changes for maintainability and dead code?

The best way to audit code changes for maintainability is to evaluate readability, modularity, and descriptive naming while actively identifying and avoiding dead code to ensure long-term quality.

Can I use a structured checklist to catch hardcoded secrets and insecure configurations?

Yes, you can use a structured checklist to catch hardcoded secrets, insecure configurations, weak authentication, and insecure input handling during code reviews to ensure security gaps are identified and communicated consistently.