vtmocanu
@vtmocanu
Public Skills
uzi-cli
by vtmocanu
Drive the uzi factory from the terminal with the installed uzi CLI — list/inspect/approve/steer runs, read the judge's review, manage workers and repos, and read admin state. Built for agents (--json, documented exit codes) as much as humans. Say "send to uzi" or "ship to uzi" to drive a PRD issue to a merged, green MR (an Auto-mode orchestration).
uzi-release
by vtmocanu
"Cuts and ships a uzi release for this repo (hosted on GitHub), and nothing else: confirms nothing wanted in the release is still unmerged and main's CI is green, then cuts the release (RC-first version bump, CHANGELOG, tag, GHCR publish, deploy verify) INLINE as the lead with the bundled release-cut/release-watch/release-verify scripts and presents the summary while it publishes in the background. Reviewing and merging open PRs, Renovate included, is the uzi-lander skill. Use when the user runs /uzi-release, or asks to cut or ship a uzi release, promote an RC, bump the uzi version, or deploy uzi. Triggers include uzi-release, release uzi, cut a uzi version, cut an RC, promote the RC, ship uzi, deploy uzi."
uzi-watcher
by vtmocanu
"Dispatches one or more uzi PRD issues in Auto mode on this GitHub-hosted repo and steers each to an approved plan: makes the issue eligible, creates the gated run, reviews, revises or approves the plan (plan-trap checks, e.g. workflow edits, cookie-only routes, gate mechanics), then hands the running run to uzi-lander, which lands its PR. Owns uzi's workflow-scope guardrail (the worker PAT cannot push .github/workflows changes), proactive backups of in-flight run work from hosted worker PVCs (scripts/backup-runs.sh, scripts/backup-loop.sh), and recovery of a lost, push-rejected or secret-blocked run's commits plus uncommitted work. Use when the user says send or ship an issue to uzi, watch a uzi run to its plan gate, steer a plan, run several uzi runs in parallel, back up the runs, or recover a lost run's work. Triggers include send it to uzi, uzi auto mode, uzi watcher, back up the runs, snapshot in-flight work, recover a lost run, recover a run's work from the worker PVC."
uzi-lander
by vtmocanu
"Lands a uzi run's pull request on this GitHub-hosted repo, taking over at any point after dispatch: polls a running run blind to its terminal state, decides whether Renovate-class PRs need independent review, chooses local or bot reviewers for other PRs by risk, handles findings, uzi's own mr_rework, local fixes, rebase and migration renumbering, the admin merge and post-merge CI, reporting one status line per state change. Also lands the whole open-PR set in order (reds, ours, then Renovate) and owns the dependency-PR rules. Claims each PR in a shared per-repo board so several landing sessions (Claude or Codex) coordinate priority and quota; deterministic steps are bundled scripts. Use when the user says take over run X, land PR N, babysit or drive home the PR, wait for CodeRabbit, fix the review findings, or merge the open or renovate PRs. Triggers include take over the run, land the PR, uzi lander, CR rate limited, greptile review, merge it when green, merge the uzi PRs, land the batch."
issue-triage
by vtmocanu
"Triages GitHub issues on this repo into queued or parked decisions. Checks spent one-shot schedules, prioritizes non-maintainer reports, finds selector/eligibility gaps and missing area or priority labels, then checks the backlog and parked issues. Verifies claims against current code and merged PRs, recommends a verdict and taxonomy labels, and applies confirmed changes with a freshness comment. Picks small, low-risk issues for the on-deck sweep (no plan review), splits mixed ones, and rewrites their bodies into pinned specs. Queue audits predict and verify the next sweep's picks. Use when triaging or prioritizing the backlog, finding issues the sweep never fires, or deciding what to send to uzi. Triggers include triage issue, triage the backlog, categorize issues, prioritize the backlog, un-sweepable issues, next issue to implement, should we do this issue, queue an issue for uzi, clean up fired schedules, what goes to the sweep tonight, what can go on-deck, label on-deck."
judge-triage
by vtmocanu
Triages uzi judge recommendations from backlog to resolution. Loads the uzi-cli skill to fetch all open recommendations, asks the user which category to work, bundles that category into quick-wins and high-impact groups, screens false positives, drives the fix, then resolves or dismisses each in the judge after the user confirms. Agent categories (improve_agent, adjust_template, add_agent) are worked as one set with a three-way propagation check across the upstream vtmocanu roles.yaml, the builtin templates, and the repo .claude/agents. Use when triaging the judge backlog or working judge recommendations. Triggers include "judge recommendations", "judge backlog", "triage judge", "deal with judge recs".
prd-lifecycle
by vtmocanu
How to update a PRD file at the end of a run — scan every unchecked item, tick only what direct evidence supports, and move the file to prds/done/ when (and only when) the whole PRD is complete. Use when the issue description links a prds/*.md file and you are about to signal the work done, or when reviewing another agent's PRD update.
ui-screenshots
by vtmocanu
"Captures clean, demo-masked uzi web UI screenshots in BOTH light (Dawn) and dark (Ember) themes for the blog and README, fast and deterministically. Drives a logged-in Chrome over CDP - ensures demo mode on, flips instance branding to vanilla (built-in uzi mark, no powered-by) then restores it, forces each theme, leak-scans, and captures the app viewport at 2x with no browser chrome. shots.json is the manifest of every screenshot and where it lands. Use when capturing or refreshing uzi UI screenshots for the blog or README. Triggers include uzi screenshots, blog screenshots, readme screenshots, refresh the screenshots, screenshot the uzi UI, regenerate screenshots."