review-scope-structure-abstraction

Analyze pull request diffs for structural and duplication risks.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/D3Hunter/ai-engineer --skill review-scope-structure-abstraction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-scope-structure-abstraction
Source: https://github.com/D3Hunter/ai-engineer/tree/main/skills/review-scope-structure-abstraction
Command: npx skills add https://github.com/D3Hunter/ai-engineer --skill review-scope-structure-abstraction

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of undetected maintainability and structural risks in pull requests that lead to long-term tech debt, tight coupling, and costly post-merge regressions.

Core Features & Use Cases

  • Static PR Structure Analysis: Reviews pull request diffs for package cohesion issues, incorrect logic layer placement, and unextracted code blocks with multiple responsibilities.
  • Duplication Risk Detection: Sweeps for duplicate definitions, SQL fixture collisions, and unnecessary abstractions that add indirection without clear reuse or clarity value.
  • Use Case: Engineering teams can use this during code review to catch structural issues early, ensuring codebases stay maintainable, aligned with architectural boundaries, and free of hidden duplication risks before merge.

Quick Start

Use the review-scope-structure-abstraction skill to analyze your open pull request's diff for structural and duplication risks, then receive a prioritized list of findings with severity ratings and fix recommendations.

Frequently Asked Questions about review-scope-structure-abstraction

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

FAQPage Schema
How do I detect code duplication and structural risks in a pull request?

To detect code duplication and structural risks in a pull request, analyze the PR diff for package cohesion issues, incorrect layer placement, and duplicate definitions to generate severity-rated findings.

What is static analysis for code structure and encapsulation in PR review?

Static analysis for code structure and encapsulation reviews behavior-changing pull request diffs without executing builds or tests, identifying unextracted code blocks and unnecessary abstractions that cause tech debt.

Does this static code review require running build or test commands?

No, this static code review does not require running build or test commands. It analyzes pull request diffs directly to identify maintainability risks and structural issues like package cohesion and layer placement.

How do I check package cohesion and layer placement before merging a pull request?

Check package cohesion and layer placement before merging by sweeping the pull request diff for structural risks and duplicate definitions, producing standardized severity-rated findings for code review.

Can I detect SQL fixture collisions and unnecessary abstractions during code review?

Yes, you can detect SQL fixture collisions and unnecessary abstractions by applying static analysis to your pull request diff, catching duplicate definitions and indirection lacking clear reuse value before merge.