Two-phase code verification. Phase 2 runs static analysis in parallel (lint, format, unit tests -- commands auto-detected from project stack). Phase 3 runs integration and E2E tests sequentially. Presents executive summary with MERGE_READY or NEEDS_FIX verdict. Supports Go, TypeScript, Python, and any project with a Makefile.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "optimus-verify-code" with this command: npx skills add alexgarzao/skillsmp-alexgarzao-alexgarzao-optimus-verify-code
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Stage 2 of the task lifecycle. Executes a validated task specification end-to-end: identifies the task, loads context from Ring pre-dev artifacts, questions ambiguities upfront, then delegates execution to the dev-cycle skill. Commits only after user approval.
Import Ring pre-dev artifacts into optimus format. Reads task specs and subtasks from Ring's pre-dev output, creates tracking overlays (tasks.md + T-NNN.md). Re-runnable — only imports what's new. Never deletes original files.
Stage 1 of the task lifecycle. Validates a task specification against project docs BEFORE code generation begins. Catches gaps, contradictions, ambiguities, test coverage holes, and observability issues. Analysis only -- does not generate code.
Stage 3 of the task lifecycle. Validates that a completed task was implemented correctly: spec compliance, coding standards adherence, engineering best practices, test coverage, and production readiness. Uses parallel specialist agents for deep analysis, then presents findings interactively. Runs AFTER optimus-build finishes to validate code quality and spec compliance before the task can proceed to PR review or close.