runnable-verify

Audits dependencies and verifies startup across Node, Python, Rust, Go, .NET, and Unity.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/igot-ai/os-twin --skill runnable-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runnable-verify
Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/qa/runnable-verify
Command: npx skills add https://github.com/igot-ai/os-twin --skill runnable-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures that code is actually runnable — not just that it compiles. It validates dependencies, checks for version conflicts, attempts to start the application, and provides actionable fix instructions when issues are found.

Core Features & Use Cases

  • Dependency auditing to detect ecosystem and new/modified dependencies.
  • Phase-based runtime verification across common ecosystems (Node.js, Python, Rust, Go, .NET, Unity).
  • Generation of practical fix instructions when runnable issues are detected.
  • Integration-ready workflow: dependency audit, clean install, runtime verification, and reporting.

Quick Start

Run runnable-verify in your project root to audit dependencies, attempt startup, and generate actionable fixes.

Frequently Asked Questions about runnable-verify

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

FAQPage Schema
How do I verify my code is actually runnable before handing off to QA?

Runtime verification audits dependencies, detects version conflicts, attempts application startup, and generates actionable fix instructions to catch blockers before QA. This ensures code runs correctly across supported ecosystems rather than just compiling.

What ecosystems does runtime verification support for dependency auditing?

Runtime verification supports dependency auditing and startup checks across Node.js, Python, Rust, Go, .NET, and Unity ecosystems. It detects new or modified dependencies and validates them to prevent runtime conflicts.

How do I detect dependency conflicts causing startup failures?

To detect dependency conflicts causing startup failures, run a clean install check followed by a startup verification attempt. The audit identifies ecosystem-specific dependency issues and generates practical fix instructions for any conflicts found.

When should I run dependency and startup verification in my workflow?

Run dependency and startup verification during epic handoffs and before QA to catch runtime blockers early. This phase-based approach ensures code is actually runnable and prevents integration issues from reaching downstream stages.

Can I get actionable fix instructions when runtime issues are detected?

Yes, when runtime issues are detected during verification, the system generates practical fix instructions addressing detected dependency conflicts and startup failures. These instructions guide developers through resolving specific runnable code problems.

What is the difference between code that compiles and code that is actually runnable?

Code that compiles passes syntax and type checks, while code that is actually runnable successfully resolves dependencies, starts without conflicts, and executes at runtime. Runtime verification validates the latter by attempting clean installs and application startup.