thermo-nuclear-code-quality-review

Review code changes for maintainability issues against a specified branch.

1|Updated May 31, 2026

Search Tags:#code quality #code review #code analysis #maintainability #architectural review

Ready to run

npx skills add https://github.com/kyn0v/Binwak --skill thermo-nuclear-code-quality-review-kyn0v

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: thermo-nuclear-code-quality-review
Source: https://github.com/kyn0v/Binwak/tree/main/.github/skills/thermo-nuclear-code-quality-review
Command: npx skills add https://github.com/kyn0v/Binwak --skill thermo-nuclear-code-quality-review-kyn0v

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a thorough maintainability review for code changes, identifying potential issues with abstractions, file sizes, and architectural drift.

Core Features & Use Cases

Maintainability Review: Checks for abstractions, file size changes, branching issues, type boundaries, and architectural drift.
Scope: Reviews only the changed code from a specified branch or the default 'main'.
Use Case: Use this Skill to assess the impact of recent code changes on the maintainability and scalability of your codebase.

Quick Start

Run the code quality review for the 'feature-branch' using the 'thermo-nuclear-code-quality-review' skill.

Frequently Asked Questions about thermo-nuclear-code-quality-review

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

FAQPage Schema

How do I perform a maintainability review on code changes from a feature branch?▼

Code maintainability analysis detects architectural drift, file size changes, and abstraction issues by comparing the current codebase against a specified branch. It focuses strictly on the changed code to assess impact on scalability and maintainability.

What is architectural drift in a codebase and how is it detected during code review?▼

Architectural drift is the gradual divergence of code structure from its original design. During a code review, it is detected by analyzing type boundaries and branching in changed files to prevent structural degradation in complex projects.

How do I check file size and branching issues in changed code before merging?▼

You can check file size changes and branching issues by running a code quality review on your feature branch. This process evaluates the changed code against the main branch to highlight maintainability risks and type boundary violations.

Can I use this code review process for large and complex software projects?▼

Yes, this code analysis process is specifically designed for large or complex projects. It evaluates abstractions, file sizes, and type boundaries within changed code to maintain architectural integrity during code review workflows.

Do I need a specific branch comparison to analyze code maintainability?▼

Yes, you need to compare your current codebase with a specified branch or the default main branch. This comparison is required to isolate the changed code for a thorough maintainability and architectural drift review.