skills.rest
1thirteeng3
1thirteeng3COMMUNITY
Explore all skills by this author →
GitHub

code-review

Automate code reviews for security and quality issues across multiple languages.

Updated Mar 24, 2026
Search Tags:#security#quality#best-practices#static-analysis#error-handling#code-review#pull-requests
One-click install
npx skills add https://github.com/1thirteeng3/greenmoire --skill code-review-1thirteeng3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/1thirteeng3/greenmoire/tree/main/integrations/hermes-agent/skills/software-development/code-review
Command: npx skills add https://github.com/1thirteeng3/greenmoire --skill code-review-1thirteeng3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a repeatable, security-focused framework for code reviews to identify vulnerabilities, quality gaps, and maintainability issues before changes merge into the codebase.

Core Features & Use Cases

  • Security First: detect hardcoded secrets, validate input, ensure safe authentication/authorization checks.
  • Error Handling: require try/catch around external calls and clear, context-rich logging.
  • Code Quality: enforce single-responsibility functions, descriptive names, no dead or duplicated code.
  • Testing Considerations: encourage coverage for edge cases and both success and failure paths.

Quick Start

Run a pull request review using the checklist to ensure security, error handling, and quality standards are met.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code reviews for security vulnerabilities in pull requests?▼

Automate code reviews by applying a security-first checklist to pull requests, validating input, detecting hardcoded secrets, and enforcing parameterized queries before merging code changes.

What should a code review checklist include for error handling and code quality?▼

A code review checklist should require try/catch blocks around external calls, context-rich logging, single-responsibility functions, descriptive names, and the elimination of dead or duplicated code.

Can I use a static analysis checklist to audit existing code for hardcoded secrets?▼

Yes, you can audit existing code across multiple languages using a security-focused checklist to detect hardcoded secrets, verify safe authentication, and identify maintainability issues.

How do I ensure my code changes cover edge cases and failure paths?▼

Ensure robust code changes by enforcing testing considerations that require coverage for edge cases, validating both success and failure paths during the pull request review process.

Does this code review approach work across multiple programming languages?▼

Yes, the security-first and quality-focused checklist applies to code changes and existing code audits across multiple programming languages to identify vulnerabilities consistently.

Why should I use a security-first checklist instead of a general code review process?▼

A security-first checklist prioritizes input validation and safe authorization checks, establishing a repeatable framework to catch vulnerabilities before general code quality gaps are addressed.

Related Skills

Explore More Software Engineering Skills→
horizontalsystemshorizontalsystems

aif-review

Review staged changes or pull requests for correctness, security, and maintainability issues.

Official
Advanced
plurigridplurigrid
60

code-review

Automate code review for security, quality, and performance issues in pull requests.

Official
Intermediate
hoavdchoavdc
21

codexkit-test-hardening

Improves code quality by hardening unit and integration tests around changes.

Community
Intermediate
OWASPOWASP
141

secrets-scan

Detect hardcoded secrets in source code and configuration files.

Official
Intermediate