Menu
SkillsMP has collected 45 skills from HiQS-Labs/XYZ-forge. Open a skill to review its source and details.
Showing 40 of 45 collected skills.
Drive an automated /relay review loop on THIS repo with the shipped relay-automation harness (relay-drive.sh + codex-turn.sh / agy-turn.sh / poll.sh) rather than improvising the handoff by hand. Use when the operator wants to "run an automated relay", "have…
Diagnose CI health and, when needed, benchmark a config change side by side — without re-deriving either from scratch each time. Use when the operator asks "why is CI slow", "diagnose our CI", "is our CI healthy", "what's the bottleneck", or wants to compare…
Deterministic, multi-model code review system and skill for XYZ. Summon frontier reviewers (Command Code -> Qwen 3.8-Max, GLM-5.3, OpenRouter, Codex, Agy) to perform throwaway-worktree isolated code reviews on local diffs or GitHub PRs. Validates…
Session-scoped triage: what did I leave open, what is rotting, and is the plan still right — answered in under a screen. Runs in seconds over the session, the working tree, open PRs, and the two ledgers (ROADMAP + RELEASES DB), then emits a ranked list capped…
Start or join a local XYZ discussion shared by two or more Claude, Codex, or other agent sessions through a compact six-digit ID. Use when a prompt says “Join XYZ AgentChorus #123456 as agent number two… — use the agent-chorus skill” (older invitations omit…
Find the subsystems that should be one subsystem. Traces a codebase resource-first instead of subject-first, then reports every place N independent paths reach the same table, file, env var, endpoint, binary, or config key without ever meeting — or where N…
ATE (Automated Testing Environment): drive long-running (2-3hr+) unattended variation-test suites against the Aider, OpenRouter, and GLM 5.2 pipeline using a local Gemma model in LM Studio as the worker, with periodic frontier-model check-ins for drift…
File a bug against the xyz-3-agents-swarm harness from ANY repo or session — lands a PDDA-compliant capture in that repo's PROJECT/1-INBOX/ (GH-<n>-*.md), files the tracking GitHub issue, and parks a one-line ROADMAP pointer, without touching the repo you are…
Draw an interactive system architecture or Git-history diagram for a repo. Architecture maps start from existing rendered knowledge (graphify, codebase-memory, RAG, architecture docs) before raw code. Git-history maps render commits, branch cuts, and merges…
Pressure-test an option set before the operator picks. Catches an AI agent — this one included — conflating two separate problems into one menu, or quietly narrowing the field to a false dilemma that skips the boring option. Borrows debug-mantra's…
Convert a highly technical document or subject into a plain, accurate, layman-friendly explanation using Feynman-style teaching moves — everyday analogy, a first-principles ladder, jargon stripping, and honesty about the limits. Use this whenever the user…
Walk a repo's front door as a brand-new user would and report whether they can actually get from clone to working — not just whether the docs exist. Use whenever the user asks to audit, review, or critique a repo's onboarding, installation, setup,…
Diagnose and fix the "git push works but `gh` fails" auth split on macOS — where the GitHub CLI and git consult different credential stores and drift apart — non-destructively, without over-engineering. Trigger when the user says "git push works but gh…
Produce an honest, defensible ground-truth read of the current repo — how mature the codebase really is, how far along each feature actually is, and what can be safely claimed about it externally. Reads CHANGELOG, architecture/technical docs, and recent git…
Get an unfamiliar repo installing and building locally, fix only what blocks it, and open a PR carrying the fixes plus an append-only change log. The deliverable is a working build and a PR — never a findings report. Trigger when the user says "install this…
Project plan enhancement tool. Reads a phased planning doc and appends a QA checklist (DRY, SOLID, observability, and phase-appropriate litmus tests) under each phase, and optionally adds an anti-goals section to give each checklist a scope boundary, and…
Add a curated set of read-only permission rules -- file reads, directory listings, content search (grep/glob), git inspection, and system checks -- to a Claude Code settings.json allowlist so safe reads stop triggering permission prompts. Local read-only by…
Audit a repo's root README as both the artifact under review and the map to everything else — checking accuracy, legibility, understandability, and operator UX, then following every pointer it makes to other docs as a litmus test for the whole repo's doc…
Trace an existing system end to end — entry points, call paths, every read and write of the state involved, the contracts crossed, the failure and rollback paths — and write it down as a Recon Map before a plan for changing it is drafted. Fires when the user…
Generate and run a relay thread file in `relay-system/<date>/<slug>.md` — a turn-based, file-based review loop between two Claude Code agents (a Producer who builds, a Reviewer who critiques and proposes fixes the author applies) so a human stops copy-pasting…
Review the most recent permission requests in the current session, generalize them into safe allowlist rules, and append them to .claude/settings.local.json to reduce future prompts. Triggers when the user runs "/rpr", "/rpr <N>", "/rpr session", or says…
Audit a script-calling skill for CWD-sensitive path-resolution bugs — bundled `.sh` scripts that run in the session that wrote them but come back "not found" in another session, repo, or install — then write a graded report with a proposed fix. Runs a…
Interrogate authority before planning a feature, refactor, migration, rewrite, backfill, event-sourcing design, dual-write setup, new authoritative store, or system-of-record change. Fire whenever a proposal might introduce, move, duplicate, or replace…
Apply an opinionated software-engineering governance lens to a build/spec/PRD document — especially a "build v1.x" doc — so the plan enforces minimal scope, designs for diagnosis, accounts for blast radius, and is verifiable before anyone writes code. Use…
Give a git repo a stable, distinct VS Code background tint so windows are tellable apart at a glance. The color is scoped to the workspace (.vscode/settings.json under workbench.colorCustomizations), so it applies every session with no per-session step. Two…
Read two or more Convergence Maps produced by /dry — across repos, or across re-runs of one repo — and find what repeats. Clusters findings by SHAPE rather than by resource, so "a gateway exists and the files that import it bypass it anyway" surfaces as one…
Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix.…
Apply three lenses to one problem in a fixed order — recon (what is actually there), debug-mantra (is what I believe actually true), ponytail (what is the smallest thing that works) — with an explicit rule for how much evidence to buy before shrinking. Use…
Immediate serial task queue execution engine and conversational capture skill. Use when an operator wants to queue, prioritize, inspect, or execute a sequence of tasks one at a time today without marathon wave planning or concurrency overhead. Re-uses the…
Sweep GitHub issues opened or updated in an age window (default: last 10 days; the window is adjustable, e.g. an 11-14-day slice to avoid overlapping another sweep), verify each one is still valid, reproducible, and not already fixed (fan out subagents to…
Per-repo strategic compass over the last 2-3 weeks of activity. Reports the Run/Grow/Transform flow distribution (are we treading water or moving the needle), clusters recurring defects into high-value fix targets ranked by what one durable fix would retire,…
Tick-backed, self-healing automation for the file-based /relay review loop — a hands-free poll driver (poll.sh), a relay-turn supervisor (relay-drive.sh), a liveness watchdog (watchdog.sh), a verdict-gated runner (runner.sh), and headless cross-model…
Hotfix fast lane (GH-267) for an explicit `/express`, "express this hotfix", or "express GH-N" request. Carries a critical, risk-bounded fix, registered regression suite, releases-ledger updates, born-complete PDDA doc, CHANGELOG, landing, and reconciliation…
Resolve a colloquial OpenRouter model name (e.g. "GLM 5.2", "Nemotron Ultra 3") to its canonical `provider/slug[:variant]` id BEFORE setting `AIDER_MODEL` for `aider-turn.sh`, `consult.sh --models aider`, or `DEEP_RESEARCH_OPENROUTER_MODEL` for…
One-shot cross-model CONSULT — fan the same question out to Codex and agy in parallel (repo-isolated, advisory), then reconcile their answers into one. Use when the user wants a "second opinion", to "ask Codex and agy", a "panel" or "cross-model" check, or an…
Read, synthesize, diagnose, clean, author, and publish the optional RELEASES.md planning ledger through one routed workflow. Use for /releases; release status or health checks; stale-plan review against merged PRs, commits, and CHANGELOG entries; disciplined…
HQ — the multi-repo command center. Turn a single utterance ("For project Acme, do X") into governance-aware action across every repo on this device. Resolves a project name (fuzzily) to a real repo via the registry ladder (Rebalance project_registry → XYZ…
Audit active PDDA marathon plans and bundles, reconcile every lane against canonical project docs, frontmatter and status tables, GitHub issue and PR state, landed commits, tests, and CHANGELOG evidence, then archive only verified-complete task docs and fully…
Triage PDDA intake and active work into a ranked, preflight-checked, collision-safe marathon candidate list. Reconcile GH capture docs with live issue state, identify missing or stale preflight contracts, run dry-run readiness checks, and group disjoint…
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the added code, abstraction, dependency, or automation needs to exist at all to satisfy the stated requirement…