skills.rest
mariari
mariariCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Identify architectural misfits, dead code, and excessive complexity in code artifacts.

17|5|Updated Mar 22, 2025
Search Tags:#architecture#complexity#refactor#code-review#pull-request#dead-code
One-click install
npx skills add https://github.com/mariari/ElixirGtBridge --skill code-review-mariari
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/mariari/ElixirGtBridge/tree/main/.claude/skills/code-review
Command: npx skills add https://github.com/mariari/ElixirGtBridge --skill code-review-mariari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently validating code quality by identifying architectural misalignments, dead code, and unnecessary complexity, reducing defects in modules, files, or PRs.

Core Features & Use Cases

  • Architectural assessment: evaluates whether code structure aligns with intended architecture and design principles.
  • Dead code detection: surfaces unused or unreachable code paths for removal or refactoring.
  • Complexity insights: highlights high cyclomatic complexity and hotspots to prioritize fixes.
  • Use Case: During a PR review, run the reviewer to surface architectural violations and recommended refactors.

Quick Start

Provide a direct instruction to initiate the code review on the target code path.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I identify architectural risks and dead code in a pull request?▼

To identify architectural risks and dead code in a pull request, run a targeted code review that evaluates modules and files for architectural misalignments, unreachable paths, and excessive cyclomatic complexity to prioritize refactoring.

What is cyclomatic complexity and how does it affect code refactoring?▼

Cyclomatic complexity measures the number of independent execution paths in code. High complexity hotspots indicate areas requiring refactoring to reduce structural difficulty and lower the likelihood of introducing defects.

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

Yes, this code review approach works across different programming languages and repositories. It applies deterministic evaluation criteria to assess architectural alignment, dead code, and complexity in modules, files, and pull requests universally.

How do I detect unused or unreachable code paths during a PR review?▼

To detect unused or unreachable code paths during a PR review, apply dead code detection to surface unnecessary code artifacts. This identifies unused modules and files for removal or targeted refactoring before merging.

When should I evaluate code structure alignment against intended architecture?▼

You should evaluate code structure alignment during pull request reviews and development workflows. This architectural assessment catches design principle violations early, reducing defects and ensuring modules and files match the intended architecture.

What is the best way to reduce excessive complexity in code modules?▼

The best way to reduce excessive complexity in code modules is to run a structured review that highlights high cyclomatic complexity hotspots. Use these deterministic insights to prioritize targeted refactoring and remove structural dead code.

Related Skills

Explore More Software Engineering Skills→
purduehackerspurduehackers
4

pull-requests

Manage GitHub pull request creation, updates, reviews, and merging.

Official
Intermediate
NAKKA-KNAKKA-K

refactoring

Plan safe code refactors to reduce complexity and eliminate dead code.

Community
Advanced
dreamingechoesdreamingechoes
2

code-review

Generate structured code review feedback with severity-classified findings and fixes.

Community
Advanced
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate