backend-code-quality-review

Name: backend-code-quality-review
Availability: InStock
Author: Infraspec

Review backend source code for design smells and maintainability issues.

3|Updated Mar 10, 2026

Search Tags:#architecture #code review #backend #solid #coupling #naming #dry

Ready to run

npx skills add https://github.com/infraspecdev/tesseract --skill backend-code-quality-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backend-code-quality-review
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/backend/code-quality-review
Command: npx skills add https://github.com/infraspecdev/tesseract --skill backend-code-quality-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch backend code that is hard to evolve because of design smells like vague responsibilities, duplicated logic, unnecessary abstraction, and brittle coupling.

Core Features & Use Cases

Structural Code Review: Evaluates service, domain, controller, and repository code for SOLID, DRY, KISS, YAGNI, naming, cohesion, and dependency-direction issues.
Backend Stack Awareness: Triggers on common backend projects in Java, Kotlin, Python, Node/TypeScript, and Go.
Practical Use Cases: Use it when reviewing a feature branch, auditing a new module before merge, or shaping a design plan before implementation.

Quick Start

Ask the assistant to review the selected backend files for code-quality smells and return grouped findings with file paths, line ranges, severity, and a one-sentence recommendation for each issue.

Frequently Asked Questions about backend-code-quality-review

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

FAQPage Schema

How do I review backend code for design smells and maintainability issues?▼

Backend code review for structural smells checks services, controllers, and repositories against SOLID, DRY, KISS, YAGNI, and coupling principles. It identifies vague responsibilities, duplicated logic, and unnecessary abstractions that make backend services hard to evolve and maintain.

Can I run a structural code review on Python and Node TypeScript backend projects?▼

Yes, structural code review supports backend projects in Java, Kotlin, Python, Node/TypeScript, and Go. It evaluates domain models, controllers, and repositories across these stacks to identify naming issues, dependency direction problems, and interface segregation violations during change reviews or module audits.

How do I audit a backend module for SOLID violations before a merge?▼

Auditing a backend module for SOLID violations involves evaluating single responsibility, interface segregation, and dependency direction within the changed files. The audit reports specific structural design smells with file paths, line ranges, severity levels, and one-sentence recommendations for each identified issue before the merge.

What is the best way to check coupling and cohesion issues in backend source code?▼

The best way to check coupling and cohesion issues is evaluating dependency direction and structural relationships between modules. This approach detects brittle coupling and poor cohesion in backend services, returning grouped findings with file paths, line ranges, severity, and actionable recommendations for each violation.

When do I need a pre-implementation design check for backend services?▼

A pre-implementation design check is needed when shaping a design plan to prevent backend code that is hard to evolve. It catches structural design smells like unnecessary abstraction and vague responsibilities before implementation begins, ensuring the planned architecture adheres to KISS and YAGNI principles.

What backend code quality issues does a structural review report?▼

A structural backend code review reports SOLID, DRY, KISS, YAGNI, naming, cohesion, coupling, and dependency-direction issues. Findings are grouped by severity and include specific file paths, line ranges, and a one-sentence recommendation to address the identified design smell or maintainability issue.