code-review

Review code changes and pull requests against a security-first checklist.

Updated Apr 10, 2026

Search Tags:#testing #security #quality #review #best-practices #code-review #pull-requests

Ready to run

npx skills add https://github.com/KarlinskyS/hermesSkills --skill code-review-karlinskys

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/KarlinskyS/hermesSkills/tree/main/software-development/code-review
Command: npx skills add https://github.com/KarlinskyS/hermesSkills --skill code-review-karlinskys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews are error-prone and time-consuming without a structured, security-focused checklist that can be consistently applied across teams.

Core Features & Use Cases

Security-first checks: Validate input handling, authentication, and secret management during reviews.
Quality and maintainability: Promote code readability, modular design, and adherence to style guidelines.
Collaborative feedback: Provide actionable, non-ambiguous feedback templates that improve PR quality and team learning.

Quick Start

Review a new pull request by applying the security-first checklist, capturing issues, and suggesting concrete fixes in the review comments.

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 security-focused code review on a pull request?▼

Perform a security-focused code review by applying a structured checklist that validates input handling, authentication, and secret management. This approach ensures pull requests are consistently evaluated for vulnerabilities before merging.

What is a security-first checklist for code reviews?▼

A security-first checklist for code reviews is a structured protocol that prioritizes validating input handling, authentication, and secret management to catch vulnerabilities early. It solves the problem of error-prone manual reviews by enforcing consistent security standards.

Can I use this code review approach across different programming languages and projects?▼

Yes, you can use this code review approach across different programming languages and projects. The review workflow applies quality guidelines, testing considerations, and security checks universally to improve code maintainability.

How do I write actionable feedback for a pull request review?▼

Write actionable feedback for a pull request review by using structured templates that provide concrete, non-ambiguous suggestions for fixes. This promotes code readability, modular design, and team learning during the collaborative review process.

What's the best way to audit existing code for security and quality?▼

The best way to audit existing code for security and quality is to apply a structured, security-focused checklist that captures issues and suggests concrete fixes. This enforces best practices, testing considerations, and quality guidelines across the codebase.

Why does my code review process lack consistent quality and maintainability checks?▼

Your code review process lacks consistent maintainability checks because it operates without a structured, security-focused checklist. Applying standardized quality guidelines for readability and modular design resolves this inconsistency across teams.