verifier-installer

Installs format, build, test commands and a CI workflow into repositories lacking a verify loop.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/dhanesh/agent-skills --skill verifier-installer-dhanesh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verifier-installer
Source: https://github.com/dhanesh/agent-skills/tree/main/verifier-installer
Command: npx skills add https://github.com/dhanesh/agent-skills --skill verifier-installer-dhanesh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Many repositories lack a runnable verification loop — no test command, no CI, no documented build — which blocks agents and developers from confirming changes work. This Skill detects the stack, proposes a plan, installs the missing verifier entrypoints plus a GitHub Actions workflow, and proves the loop by demonstrating a red-to-green cycle. ## Core Features & Use Cases - Deterministic stack detection: A bundled offline Python script scans the repo (python, node, go, rust, make) and emits a JSON plan of existing verifiers, missing rails, and concrete proposals, reporting malformed manifests as errors instead of crashing. - Per-stack install playbooks: Reference guides provide exact Makefile targets, package.json scripts, smoke tests, and CI workflow snippets for each detected stack, extending existing files rather than overwriting them. - Prove-the-loop protocol: Each installed rail is verified by intentionally breaking something trivial, watching the verifier fail, and reverting to green — unproven rails are honestly reported. - Use Case: After an agent-ready-rails audit reports a repo has no tests or CI, ask the agent to set up the verify loop; it detects a Node project, adds npm test/build scripts and a verify.yml workflow, and demonstrates the loop catching a deliberate break. ## Quick Start Ask the agent to set up the verify loop, tests, and CI for this repository.

Frequently Asked Questions about verifier-installer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up tests and CI for a repo that has none?▼

Run the bundled detect_stack.py script against the repo to get a JSON plan of missing rails, confirm the plan, then install per-stack verifier commands and a GitHub Actions workflow. Each rail is proven by breaking something trivial and watching it go red then green.

What stacks does the verifier detection script support?▼

The detector recognizes python (pyproject, setup, requirements with pytest or unittest), node (package.json scripts and lockfiles), go (go.mod), rust (Cargo.toml), and Makefile targets, plus existing GitHub Actions workflows. Detection is offline and stdlib-only.

Does it work with CI providers other than GitHub Actions?▼

GitHub Actions is the default provider, generating .github/workflows/verify.yml. If you name another provider such as GitLab CI or CircleCI, the same job is translated: checkout, toolchain setup, then the verify entrypoint.

Will it overwrite my existing Makefile or CI workflow?▼

No. The plan marks each proposal as create or extend based on whether the file exists, and existing workflows are extended rather than duplicated. A workflow is only credited as CI if it actually runs a verifier command.

When should I not use this skill?▼

Skip it when the repo already has a green verify and CI loop, since reinstalling adds noise. It also does not referee style debates: a formatter check is only wired when the repo already structurally adopts ruff or black, otherwise an honest placeholder stays red.

Why does the format rail stay red after installation on some python repos?▼

When no formatter is adopted, the format target is a loudly-failing placeholder rather than a fake check. It stays red until the owner wires a real formatter, and the install summary lists this under follow-ups instead of claiming it proven.