software-design-expert-review

Name: software-design-expert-review
Availability: InStock
Author: João Souto

Review recently changed files for APOSD design red flags and return gating verdicts.

1|Updated Jan 27, 2026

Search Tags:#code-quality #quality-gate #risk-assessment #software-design #design-review #git-diff #aposd

Ready to run

npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill software-design-expert-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: software-design-expert-review
Source: https://github.com/Joaovsales/coding-agent-workflow/tree/main/.agents/skills/software-design-expert-review
Command: npx skills add https://github.com/Joaovsales/coding-agent-workflow --skill software-design-expert-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs a focused APOSD (A Philosophy of Software Design) design review on recently changed files, scanning for the 10 red flags and mapping severities to MUST-FIX / SHOULD-FIX / NITPICK, producing a GO / HOLD / STOP verdict to guide design quality decisions.

Core Features & Use Cases

APOSD-based detection of deep design issues in modified code to prevent shallow abstractions and fragile modules.
Severity mapping to MUST-FIX / SHOULD-FIX / NITPICK with a clear gating verdict that integrates into build workflows.
Manual invocation via /skill and automated gating via /build Phase 3.5, with support for scoped reviews using --file and --scope.

Quick Start

Run the skill against your current repository state by invoking /skill:software-design-expert-review to review changed files.

Frequently Asked Questions about software-design-expert-review

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

FAQPage Schema

How do I review code changes for software design red flags before committing?▼

Review code changes for software design red flags by analyzing uncommitted or recently touched files for APOSD violations, returning findings categorized as MUST-FIX, SHOULD-FIX, or NITPICK to prevent shallow abstractions and fragile modules.

What is a quality gate for software design debt tracking?▼

A software design quality gate evaluates modified files against APOSD red flags and outputs a GO, HOLD, or STOP verdict, enabling automated gating and design debt tracking within build workflows.

How do I run a design review on specific files instead of the entire git diff?▼

Run a design review on specific files by using optional --file or --scope flags to narrow the review scope, overriding the default behavior of scanning all uncommitted or recently touched files.

Can I integrate a design risk assessment into my automated build process?▼

Integrate design risk assessment into your build process via Phase 3.5, automatically scanning changed files for APOSD red flags and producing a gating verdict to block or allow builds.

What are the APOSD red flags for shallow abstractions in modified code?▼

APOSD red flags for shallow abstractions include deep modules, information leakage, temporal decomposition, over-exposure, pass-through methods, and other design issues mapped to MUST-FIX or SHOULD-FIX severities.