skills.rest
four43
four43COMMUNITY
Explore all skills by this author →
WebsiteGitHub

reviewing-code

Standardize code reviews across repositories with readability, reliability, and security checks.

4|Updated Jan 16, 2019
Search Tags:#workflow#security#readability#quality#reliability#code-review
One-click install
npx skills add https://github.com/four43/dotfiles --skill reviewing-code-four43
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/four43/dotfiles/tree/main/claude/skills/reviewing-code
Command: npx skills add https://github.com/four43/dotfiles --skill reviewing-code-four43

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes code reviews to improve quality and security. Use when evaluating changes, after coding, or on demand to ensure consistency and risk mitigation.

Core Features & Use Cases

  • Readability: Code is simple and readable; Functions and variables are well-named; No duplicated code
  • Reliability: Proper error handling; Input validation implemented; Edge cases considered
  • Security: No exposed secrets or API keys; No hardcoded credentials; Proper input sanitization
  • Quality: Good test coverage; Performance considerations addressed; No unnecessary complexity

Quick Start

Run the review by running git diff to see recent changes, focusing on modified files, and begin the review immediately.

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I standardize code reviews for quality and security across my repositories?▼

A standardized code review evaluates changes across any repository using reproducible sections for readability, reliability, security, and feedback. This enforces consistent quality and risk mitigation throughout your workflow.

What should a code review checklist include for readability and reliability?▼

A code review checklist for readability and reliability should verify that code is simple, well-named, and duplicated code is removed. Reliability checks must confirm proper error handling, input validation, and considered edge cases.

How do I check my code changes for exposed secrets and hardcoded credentials?▼

Check code changes for exposed secrets by running a security review section that scans for hardcoded credentials and API keys. This process also ensures proper input sanitization is implemented to mitigate security risks.

Can I run a code review on demand using git diff for modified files?▼

Yes, you can run a code review on demand by executing git diff to see recent changes. The review focuses immediately on modified files to evaluate quality, security, and reliability after coding.

Does the code review process require concrete file-path references in feedback?▼

Yes, the code review process requires concrete file-path references in its recommendations. This ensures feedback is actionable and directly tied to the specific code changes under evaluation.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-diff

Identify and review exact changes across git states with unified diff output.

Official
Advanced
zm2231zm2231

code-refactoring

Refactor code to improve quality, readability, and maintainability.

Community
Advanced
nayyirahsannayyirahsan

critique

Analyze design visual hierarchy, information architecture, and cognitive load with quantitative scoring.

Community
Advanced
eliottbusinesseliottbusiness

requesting-code-review

Automate pre-commit code review with static analysis and security scanning.

Community
Advanced