solo-review
Final code review and quality gate — run tests, check coverage, audit security, verify acceptance criteria from spec, and generate ship-ready report. Use when user says "review code", "quality check", "is it ready to ship", "final review", or after /deploy completes. Do NOT use for planning (use /plan) or building (use /build).
Why use this skill?
Automate your final quality gate with solo-review. Verify acceptance criteria, run tests, audit security, and get a ship-ready report for your OpenClaw projects.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/fortunto2/solo-reviewWhat This Skill Does
The solo-review skill serves as the ultimate quality gate for any OpenClaw-managed project. It is a comprehensive, self-contained auditing tool designed to run before code deployment or as a final check after a build process. Rather than delegating tasks to external agents or sub-agents, solo-review executes a structured, multi-dimensional pipeline to ensure your codebase meets high-quality standards. It performs automated test suite execution, security audits (using pattern-based scanning for secrets), acceptance criteria verification against your project's spec.md, and dependency analysis. The outcome is a detailed, ship-ready report that provides a clear 'go/no-go' verdict based on factual data from your environment.
Installation
You can integrate this skill directly into your OpenClaw environment by running the following command in your terminal:
clawhub install openclaw/skills/skills/fortunto2/solo-review
Use Cases
- Post-Build Validation: Use it immediately after a
/buildcommand to verify that the generated code is stable and production-ready. - Deployment Readiness: Act as a mandatory checkpoint before executing a
/deploycommand to minimize the risk of shipping broken code. - Periodic Auditing: Run it on existing codebases to check for regression, adherence to architectural patterns defined in
CLAUDE.md, and potential security vulnerabilities. - Acceptance Verification: Ensure that the implemented features match the exact requirements outlined in the project's planning documentation (
docs/plan/*/spec.md).
Example Prompts
- "The build just finished successfully. Can you run a solo-review to see if we are ready to ship this version?"
- "I've completed the refactor. Please perform a final quality check to ensure the acceptance criteria in the spec are met."
- "Run a full security and quality review on the current project to identify any red flags before I merge this to main."
Tips & Limitations
- Makefile Priority: The skill is designed to respect project conventions. If a
Makefileis detected in your root directory, it will prioritizemaketargets (e.g.,make test,make lint) over generic CLI commands. Always define clearmaketargets for your workflows to get the most accurate results. - Context Awareness: The skill is not intended for planning or feature development. If you need to build code or define roadmaps, use
/buildor/planinstead. - Smart Analysis: By utilizing
codegraph_query, the skill identifies 'hub files'—the most interconnected parts of your system—to ensure audits focus on the most impactful areas of your code rather than performing random, exhaustive file scans. This optimizes performance and reliability.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-fortunto2-solo-review": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, code-execution
Related Skills
solo-swarm
Launch 3 parallel research agents (market, users, tech) to investigate an idea from multiple angles simultaneously. Use when user says "swarm research", "parallel research", "investigate fast", "3 agents", "team research", or wants faster alternative to /research. Produces research.md. Do NOT use for solo research (use /research) or idea scoring (use /validate).
solo-build
Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says "build it", "start building", "execute plan", "implement tasks", "ship it", or references a track ID. Do NOT use for planning (use /plan) or scaffolding (use /scaffold).
solo-metrics-track
Set up PostHog metrics plan with event funnel, KPI benchmarks, and kill/iterate/scale decision thresholds. Use when user says "set up metrics", "track KPIs", "PostHog events", "funnel analysis", "when to kill or scale", or "success metrics". Do NOT use for SEO metrics (use /seo-audit).
solo-audit
Health check knowledge base for broken links, missing frontmatter, tag inconsistencies, and coverage gaps. Use when user says "audit KB", "check frontmatter", "find broken links", "tag cleanup", or "knowledge base quality". Do NOT use for SEO audits (use /seo-audit) or code reviews.
solo-seo-audit
SEO health check for any URL — analyzes meta tags, OG, JSON-LD, sitemap, robots.txt, SERP positions, and scores 0-100. Use when user says "check SEO", "audit this page", "SEO score", "check meta tags", or "SERP position". Do NOT use for generating landing content (use /landing-gen) or social media posts (use /content-gen).