/optimus:verify

Verify feature branches with test plans, git worktrees, and automated checks.

70|13|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/oprogramadorreal/optimus-claude --skill optimus-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /optimus:verify
Source: https://github.com/oprogramadorreal/optimus-claude/tree/main/skills/verify
Command: npx skills add https://github.com/oprogramadorreal/optimus-claude --skill optimus-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your feature branches function correctly before merging, preventing bugs and regressions from entering your main codebase.

Core Features & Use Cases

  • Automated Verification: Runs tests, builds, and linters in an isolated sandbox.
  • Dynamic Testing: Employs AI agents to perform functional verification and code path tracing.
  • Use Case: After completing a new feature, run this Skill to automatically confirm it works as expected, catches potential issues, and provides a clear report before you request a code review.

Quick Start

Run the verify skill to check the current feature branch against its test plan.

Frequently Asked Questions about /optimus:verify

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

FAQPage Schema
How do I automate feature branch verification before requesting a code review?

Feature branch verification runs automated checks, builds, and linters in an isolated git worktree sandbox to ensure branches function correctly and prevent bugs before merging into your main codebase.

What is the best way to catch regressions in a feature branch before merging?

Catching regressions involves launching parallel AI agents for functional verification and code path tracing within an isolated sandbox, providing a clear pass or fail verdict before the branch merges.

Does automated branch verification work without manual test plan creation?

Yes, automated branch verification works without manual test plans by dynamically extracting or generating a test plan, then executing automated checks and launching AI agents to trace code paths in an isolated sandbox.

How do I handle sandbox limitations when running automated functional verification?

To handle sandbox limitations during automated functional verification, the process pauses to request human help, then reports results with a clear verdict and offers to fix the detected issues.

Can I run lint and type-check checks in an isolated environment before merging code?

Yes, you can run lint and type-check checks by creating an isolated git worktree sandbox that executes automated tests and builds alongside AI functional verification, preventing regressions from entering your main codebase.