review-master

Review documents, codebases, and architectural designs for outdated patterns and inaccuracies.

2|Updated May 26, 2026
One-click install
npx skills add https://github.com/albibenni/skills --skill review-master
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-master
Source: https://github.com/albibenni/skills/tree/main/review-master
Command: npx skills add https://github.com/albibenni/skills --skill review-master

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the risk of technical debt and architectural decay by identifying outdated patterns, security vulnerabilities, and logical flaws in your code or documentation.

Core Features & Use Cases

  • Critical Technical Scrutiny: Evaluates code and designs against current industry best practices and modern standards.
  • Pattern Identification: Detects deprecated APIs, legacy syntax, and fragile architectural choices that hinder maintainability.
  • Use Case: Use this skill to audit a legacy module before a refactor to ensure the proposed changes align with modern framework capabilities and security requirements.

Quick Start

Invoke the review-master skill to perform a critical audit of the provided architectural design document.

Frequently Asked Questions about review-master

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

FAQPage Schema
How do I perform a technical audit on a legacy codebase before refactoring?

Perform a technical audit by evaluating the legacy codebase against current industry standards to identify outdated patterns, security vulnerabilities, and logical flaws. This critical review provides actionable improvement strategies to ensure your refactoring aligns with modern framework capabilities and maintainability requirements.

What is the best way to review architectural designs for deprecated patterns?

Reviewing architectural designs for deprecated patterns involves applying critical technical scrutiny to detect legacy syntax and fragile architectural choices. Evaluating technical clarity and security ensures the design adheres to modern best practices and avoids architectural decay before implementation.

Can I use this to check if my documentation has outdated technical patterns?

Yes, you can check documentation for outdated technical patterns by performing critical technical reviews. The process identifies inaccuracies and deprecated APIs in your documents, evaluating technical clarity to ensure your documentation meets current industry standards and best practices.

Does a critical code review identify security vulnerabilities and fragile architecture?

A critical code review identifies security vulnerabilities and fragile architectural choices by evaluating your code against modern standards. It detects deprecated APIs and legacy syntax that hinder maintainability, providing actionable improvement strategies to mitigate technical debt and architectural decay.

When do I need a technical audit for software engineering workflows?

You need a technical audit for software engineering workflows when adhering to current industry standards and best practices is required. It is specifically used to evaluate technical clarity, maintainability, and security before refactoring a legacy module or finalizing an architectural design.