qa

Automate architectural reviews of code, PRs, and designs using SOLID, DRY, YAGNI, and security heuristics.

27|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/forecast-bio/ferray --skill qa-forecast-bio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/forecast-bio/ferray/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/forecast-bio/ferray --skill qa-forecast-bio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated, rigorous QA architecture reviews that enforce SOLID, DRY, YAGNI, and security standards across code, PRs, and designs.

Core Features & Use Cases

  • Framework-driven evaluation that enforces modularity, decoupling, and single-responsibility across architectures.
  • Rule-based checks for complexity, security, and maintainability with a structured severity matrix.
  • Use Case: Analysts submit a PR and request a comprehensive architectural critique to surface design risks early.

Quick Start

Submit a PR diff or architectural plan and request a formal QA review.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate rigorous code reviews for pull requests?

Automate rigorous code reviews by submitting pull request diffs or design proposals to receive a formal QA critique. This process enforces SOLID, DRY, YAGNI, and security heuristics across any tech stack to surface design risks early.

What is threat modeling in architectural code review?

Threat modeling in architectural code review evaluates security heuristics and strict criteria for modularity via the ADIHQ framework. It outputs a structured severity, dimension, location, violation, and refactor matrix to identify and address vulnerabilities.

Does this QA review process work with any programming language?

Yes, this QA review process is language-agnostic and applies to architectural roadmaps across any tech stack. It evaluates designs and pull requests based on universal principles like SOLID, DRY, and YAGNI without language dependencies.

How do I enforce SOLID and DRY principles in a design proposal?

Enforce SOLID and DRY principles in a design proposal by submitting it for a framework-driven evaluation. The review checks for complexity, modularity, decoupling, and single-responsibility, generating a rule-based severity matrix for maintainability.

What's the best way to surface modularity and decoupling risks in an architectural roadmap?

The best way to surface modularity and decoupling risks is through an automated architectural review. It applies framework-driven evaluation to enforce single-responsibility and outputs a structured severity and refactor matrix highlighting violations.