Repository guidance
Do scoped instructions explain commands, boundaries, and conventions?
PUBLIC REPOS ONLY · NO OAUTH
Find where coding agents will stall.
A deterministic readiness check for public GitHub repositories. Get a score, the evidence behind it, and the three highest-leverage fixes.
We read public repository metadata and selected setup files. No code is written, no security probing is performed, and no GitHub sign-in is required.
~60 sectypical scan
6readiness dimensions
0accounts or meetings
$49implementation pack
WHAT WE MEASURE
Not code quality.
Agent operability.
The check looks for the interfaces an autonomous coding agent needs to understand, change, and verify a repository without inventing the rules.
Deterministic setup
Can a clean environment reproduce dependencies and start the project?
Validation loop
Are tests and quality checks discoverable and runnable?
CI guardrails
Will automation catch a plausible agent mistake before merge?
Task interface
Can an agent map a request to the right files and contribution flow?
Environment safety
Are required variables documented without exposing credentials?
OPTIONAL IMPLEMENTATION PACK
From diagnosis
to commit-ready.
The $49 pack turns the public evidence into tailored starter files. It is designed to be applied asynchronously—no call, questionnaire, or private access.
$49one repository
- Tailored AGENTS.mdCommands, boundaries, and repo map grounded in detected files.
- Validation checklistA compact pre-merge loop for coding agents.
- Task packet templatesImplementation, bug-fix, and verification prompts.
- 90-day re-check guideKnow when your setup has drifted.
Scope
What this check is—and is not.
It is
A narrow, evidence-based diagnostic of repository interfaces used by coding agents.
It is not
A security audit, code review, compliance opinion, or guarantee of agent performance.
Data policy
Only public GitHub data is read. We retain the repo URL, score, and timestamp to operate the experiment.