agent-ready-rails

Audits repository readiness for coding agents and scores ten engineering rails from observed evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Teams adopting coding agents often blame the model when agents produce broken or messy PRs, when the real cause is a weak engineering system around the agent. This Skill audits a repository against ten evidence-based rails — from runnable verifiers and green CI to scoped tools and human checkpoints — and emits a severity-ranked scorecard with a prioritized fix list, so you know exactly which rail to build before investing elsewhere. ## Core Features & Use Cases - Two-tier readiness audit: Scores six Build rails (R1–R6, author → merge) on every repo, and four Operate rails (R7–R10, merge → production) when the goal is unattended agents against production, reported as separate subtotals. - Deterministic evidence collector: A read-only Python script walks the target repo and emits sorted JSON evidence per rail — test configs, CI workflows, style docs, agent context files, permission settings, CODEOWNERS — which the agent then verifies and scores 0/1/2. - Optional rail installation: On explicit request, implements the highest-leverage fixes (a single verify entrypoint, CI gating, conventions docs, architecture maps) through the repo's own PR flow, then re-verifies the improved scores. - Use Case: Before onboarding Claude Code or a background coding agent into a codebase, run the audit to discover that CI exists but never runs tests (R2 = 1) and there is no discoverable verify command (R1 = 0) — then fix those load-bearing rails first. ## Quick Start Ask the agent to audit whether this repository is ready for coding agents and produce a readiness scorecard with prioritized fixes.

Frequently Asked Questions about agent-ready-rails

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

FAQPage Schema
How do I check if my repository is ready for coding agents?▼

Run the agent-ready-rails audit against your repo. It scores six Build rails — runnable verifiers, green CI, house style, navigable context, scoped tools, and human checkpoints — from observed files and configs, then emits a scorecard with a prioritized fix list.

Why do coding agents keep producing broken or messy PRs in my repo?▼

The most common cause is a missing verify→repair loop: no single discoverable command running format, lint, build, and test (rail R1), or CI that does not gate merges (R2). The audit identifies the weakest rail from evidence so you fix the load-bearing gap first.

Does the audit modify my repository or run destructive commands?▼

No. Audit mode is strictly read-only: the collector walks the repo and emits JSON evidence without writing anything or executing migrations, deploys, or kill switches. It only writes files when you explicitly ask it to install missing rails, routed through your own PR flow.

What are the requirements to run the evidence collector?▼

The collector needs python3 with the standard library only — no external packages. It runs from any agent harness with shell access to the target repository and produces deterministic, sorted JSON output.

When should I audit the Tier 2 Operate rails?▼

Audit Tier 2 (R7–R10: observability, blast-radius containment, deploy safety, continuous re-verification) only when the goal is agents running unattended against a production system. For repos just onboarding agents to open reviewed PRs, the Tier 1 Build audit is the entire scope.

What does agent-ready-rails not cover?▼

It does not audit code correctness against real-world norms, judge code design quality, or design a single agent loop. It audits the engineering system agents run inside; sibling skills handle loop soundness, in-session context hygiene, and code-level verification.