repo-genome

Featured

7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.

AI & Automation 675 stars 86 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
94
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# repo-genome > Codex skill: 7-section readiness scorecard for a local repo — the > ADR-031 Bundle JSON Pattern surfaced through Codex (iter 110 → 114). ## What it does Answers a different question than `analyze-repo`: - **analyze-repo** — "which archetype / template / agents fit this repo?" - **repo-genome** — "is this repo READY for that harness, and what's the risk?" Produces a 7-section report: 1. **Repo profile** — type, languages, build/test commands, ci presence 2. **Agent topology** — recommended roles (maintainer / tester / security / release) 3. **MCP risk model** — surface + numeric risk + policy posture 4. **Test confidence** — how strong are the test signals 5. **Release readiness** — buildable / testable / ci-wired 6. **Recommended harness plan** — template, archetype, hosts, agents, skills 7. **Scorecard** — risk_score, publish_readiness, test_confidence LOCAL-only, deterministic, never executes repo code. Same invariant as `analyze-repo` (inherited via the shared inventory/profile pipeline). | Verdict | Exit | Meaning | |---|---|---| | `ready` | 0 | publish_readiness >= 0.75 && risk_score < 0.35 | | `needs-work` | 1 | somewhere in the middle | | `blocked` | 2 | risk_score >= 0.7 | ## Usage from Codex ``` /repo-genome path=./my-repo /repo-genome path=./my-repo bundle=true /repo-genome path=./my-repo out=./harness-genome.json ``` ## Equivalent CLI ```bash harness genome ./my-repo # text report harness genome ./my-repo --json ...

Details

Author
ruvnet
Repository
ruvnet/metaharness
Created
3 months ago
Last Updated
yesterday
Language
TypeScript
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

repo-harness-check

Verification entrypoint for repo-harness workflow readiness. Runs workflow gates, task sync, contract checks, inspector, and migration dry-run before merge or release.

435 Updated today
Ancienttwo
AI & Automation Listed

repo-status

Cross-machine status of ONE repo — this machine's clone and the peer's, side by side: uncommitted changes, unpushed and inbound commits, branch, age of the oldest pending work, convention versions still to adopt, open issues, and a one-line description of what each machine is mid-way through. Fetches both clones and auto-pulls the clean ones. Prints a short block per machine to the terminal, saying only what is not at its default. TRIGGER when: user asks "/repo-status", wants to know where a single repo stands, "what am I doing in this repo", "is this repo clean on the other machine", "does the desktop have unpushed work here", or "is this repo behind on conventions". DO NOT TRIGGER when: the question is about the fleet rather than one repo (use `/github-status`), or a plain `git status` on this machine answers it — this skill's reason to exist is the OTHER machine's clone and the columns git has no opinion about.

1 Updated today
AnotherSava
AI & Automation Listed

agent-readiness

Scores how ready a repository is for AI coding agents to work in it effectively, then remediates the gaps - grades agent instruction files, verifiable feedback loops, onboarding reproducibility, and codebase navigability against a fixed 30-signal rubric, stack-agnostic across TypeScript, Python, Go, Rust, Ruby, Java, C#, and PHP/Laravel. Activates when the user says 'is this repo agent-ready', 'readiness report', 'readiness score', 'agent readiness', 'audit this repo for AI agents', 'why do agents struggle in this codebase', 'make this repo agent-friendly', 'audit our agent instruction files', or 'score our agent readiness'. Owns the scoring and the remediation plan; defers the writing of ./docs content to vd:docs, locating code to vd:scout, public documentation sites to vd:docs site, refactoring a change toward its intended architecture to vd:simplify --aggressive, and authoring instruction files and skills to vd:skill-creator.

8 Updated 2 days ago
vanducng