Loading...
Loading...
Found 15 Skills
Use when testing app readiness, verifying runtime behavior, or validating before releases and after changes in the code. Triggers include validate, test, verify, check readiness, preview validation, build verification, TypeScript compilation.
Automated tech debt cleanup worker (L3). Reads codebase audit findings, applies safe auto-fixes for low-risk issues (unused imports, dead code, commented-out code, deprecated aliases). Confidence >=90% only. Creates single commit with summary.
Build verification, error recovery, and application of review fixes. Use this when the user mentions build verification, error recovery, applying review fixes, test failures, lint errors, or CI breaks. Do NOT load this for: implementation work, reviews, setup, or new feature development.
Use when user asks to "validate delivery", "check readiness", or "verify completion". Runs tests, build, and requirement checks with pass/fail instructions.
Use after migrating a route or completing a migration phase to verify correctness. Also use when the build breaks, tests fail, or you suspect migration regressions.
Coordinates dependency upgrades across all detected package managers
Use when users request generating unit tests for Qt modules or classes, completing test cases, or creating test files. Supports module batch generation and incremental completion.
Test voxtype in Docker containers. Use for testing builds, verifying packages work on different distros, or isolating test environments.
Builds all detected projects and verifies successful compilation
Orchestrator skill for the complete feature development lifecycle. Coordinates 5 phases - task selection, component design, build loop, analytics setup, and commit/documentation. Use when building any new feature or enhancement that requires multiple steps.
Orchestrate a multi-phase implementation workflow for this repository with artifact files under .ai/<project-name>/<letter>/ and fresh codex exec child runs per phase. Use when the user wants one prompt to drive context gathering, planning, plan assessment, implementation, build verification, and review iterations while keeping the main session context clean.
Pushes config/code and verifies builds/logs. Includes website/library push handling with tau command first, git fallback.