solo-review

Run tests, linting, security checks, and documentation verification on a codebase.

18|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fortunto2/solo-factory --skill solo-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solo-review
Source: https://github.com/fortunto2/solo-factory/tree/main/skills/review
Command: npx skills add https://github.com/fortunto2/solo-factory --skill solo-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the final quality gate for code, running tests, security checks, and code-quality audits to ensure ships are clean.

Core Features & Use Cases

  • Live MCP-assisted review: runs session and project code searches, checks acceptance criteria, and generates a ship-ready report.
  • Comprehensive checks: test suites, lints, security audits, and documentation verifications to catch issues early.
  • Use Case: after a build or deployment, invoke /review to verify readiness and receive a go/no-go verdict.

Quick Start

Run the /review skill on your project to generate a ship-ready quality report.

Frequently Asked Questions about solo-review

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

FAQPage Schema
How do I automate code review and security checks before a deployment?

To automate a code review for deployment, you can run a comprehensive quality gate that executes test suites, lints, security audits, and documentation verifications to output a go/no-go ship-readiness report.

What is ship readiness and how does a quality gate verify it?

Ship readiness verifies that code meets acceptance criteria through evidence-based checks. A quality gate enforces this by running tests, linting, and security checks, then flagging critical issues with concrete file:line references and recommended fixes.

Can I run CI-CD quality assurance checks across multiple stacks and standalone projects?

Yes, you can apply CI-CD quality assurance checks across multiple stacks and standalone projects. The review process analyzes the codebase, checks plan progress, and assesses risk to ensure project readiness regardless of the stack.

What's the best way to verify acceptance criteria and flag critical code issues?

The best way to verify acceptance criteria is by executing commands to collect test and lint results, then flagging critical code issues with concrete file:line references and recommended fixes to guide developers through risk assessment.

Why does my code pass local tests but fail the final ship readiness review?

A ship readiness review fails code that passes local tests because it enforces strict evidence-based verification across security audits, linting, and documentation, catching risks and critical issues that local test suites miss.

Do I need specific dependencies installed to perform documentation verification and code audits?

No specific dependencies are required to perform documentation verification and code audits. The review skill analyzes the codebase directly to run tests, lints, and security checks without external component dependencies.