verifier-installer

name	verifier-installer
description	Installs the runnable-verifier loop — format/build/test commands plus a CI workflow that runs them — into a repo that lacks it, turning agent-ready-rails' top finding (weak R1/R2 rails) into working files. Use when someone says "this repo has no tests or CI", "set up the verify loop", "add CI that runs the checks", "make this repo agent-ready", or after an agent-ready-rails audit scores runnable verifiers or green-CI low. Detects the stack (python, node, go, rust, make) with a shipped script, confirms a plan, writes the verifier entrypoints and a GitHub Actions workflow, then proves the loop by demonstrating a red run and repairing it to green. Not a linter-config generator for style debates, and not for repos that already have a green verify+CI loop — use agent-ready-rails to audit first; this skill installs what that audit finds missing.
license	MIT
compatibility	Requires python3 and a POSIX shell. The target repo's own toolchain (npm, go, cargo, make, pytest) is needed only to run the verifiers it already implies; detection itself is offline and stdlib-only.
metadata	{"author":"dhanesh","version":"1.0.0","tags":"verifiers,ci,github-actions,agent-readiness,test-loop,scaffolding"}

verifier-installer

Stand up the verify→repair loop in a repository that doesn't have one: a single discoverable command per rail — format, build, test — and a CI workflow that runs the same commands. This is the action-taking sibling of : rails and reports that the loop is missing (its load-bearing R1/R2 finding); this skill it. The evidence behind why this rail matters most is in that skill's grounding — a verify loop the agent cannot skip is the single highest-leverage change for agent success.