yolo

SkillDev tools

Run the repository's full local quality gate and fix failures without publishing. Use when the user types /yolo.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the yolo skill

What this skill tells your AI

The instructions your AI receives, as published by blockmatic/basilic in .agents/skills/workflow/yolo/SKILL.md and read by ahel’s review.

Purpose and inputs

Run the documented full gate (pnpm qa in Basilic, or the repo's equivalent) and fix failures. Compose lint-suite, run-all-tests-and-fix, and code-review as needed. Do not commit, push, merge, or deploy. Do not edit .env, secrets, or unrelated dotfiles. Do not delete features to make a gate pass.

Steps

  1. Run the documented lint, type, build, and test scripts from package.json. Fix owning causes. Re-run the failed command.
  2. Optionally review the task diff with /code-review (read-only). Apply fixes only for defects you can evidence.
  3. If CodeRabbit or CI comments exist and the user asked to consume them, follow coderabbit or git-pr-comments without committing.
  4. Stop when the gate is green or when remaining failures need a human (secrets, product scope, missing env).

Verification

  • Each gate command is recorded as passed, failed, or not applicable.
  • No secrets, .env, or unrelated dotfiles were edited.
  • No Git publish happened.

Handoff

Summarize failures, fixes, and remaining blockers. If they want a local commit, use /git-commit. Use /git-push only after they explicitly request publication of an already-committed branch.

Signals

GitHub stars
89
Forks
11
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
yolo-blockmatic
Source
github.com/blockmatic/basilic