skills.rest
marcusta
marcustaCOMMUNITY
Explore all skills by this author →
GitHub

code-review-checklist

Detect code smells, duplication, architecture violations, and security gaps in PR-based code reviews.

Updated May 25, 2025
Search Tags:#architecture#security#code-quality#code-review#pull-request#dry-principle
One-click install
npx skills add https://github.com/marcusta/golf-serie --skill code-review-checklist-marcusta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-checklist
Source: https://github.com/marcusta/golf-serie/tree/main/.claude/skills/code-review-checklist
Command: npx skills add https://github.com/marcusta/golf-serie --skill code-review-checklist-marcusta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews are critical to maintain quality but can be inconsistent. This skill provides a structured, repeatable process to detect smells, duplication, architecture violations, and security gaps during code reviews.

Core Features & Use Cases

  • Detect code smells and anti-patterns in changes
  • Identify DRY violations and duplication across files
  • Verify architectural boundaries and separation of concerns
  • Perform security-focused checks and generate a review report
  • Provide a reusable template for PR feedback and documentation

Quick Start

Copy this checklist and apply it to your current code changes to produce a structured review.

Frequently Asked Questions about code-review-checklist

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

FAQPage Schema
How do I run a structured code review on a pull request?▼

To run a structured code review on a pull request, apply a formal checklist that detects code smells, duplication, architecture violations, and security gaps. This process generates a final review report documenting the findings.

What should a code review checklist include to detect security gaps and duplication?▼

A code review checklist should include detection steps for code smells, DRY violations, and security gaps. It must provide a reusable template for PR feedback that verifies architectural boundaries and separation of concerns across diverse languages.

Does this code review process work for both frontend and backend code changes?▼

Yes, this code review process works for frontend, backend, and script changes. It applies to PR-based reviews across diverse languages and frameworks to identify anti-patterns and verify architectural separation of concerns.

What is the best way to identify architectural boundary violations in a PR?▼

The best way to identify architectural boundary violations in a PR is to apply a systematic review checklist. This verifies separation of concerns and detects architecture violations alongside code smells and duplication during the review.

How do I generate a final review report for code changes?▼

To generate a final review report for code changes, follow a formal review process with defined detection steps and reporting templates. This structured approach documents identified code smells, security gaps, and duplication for PR feedback.

Related Skills

Explore More Software Engineering Skills→
HillBombCreationsHillBombCreations

cmd-reviewer

Automate code review analysis across local changes, branches, and pull request diffs.

Official
Advanced
gsarmaonlinegsarmaonline

review-comments

Analyze pull request review comments and resolve failing GitHub Actions checks.

Community
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
YSheldonYSheldon

security_scan

Coordinate parallel security scanners and return prioritized vulnerability summaries.

Community
Advanced