Clean scanStatic scanned
Reviews what an Agent Skill can do and flags newly added capabilities against a reviewed baseline.
43.8k installs/moMIT
Repo Context Doctor
dhait · Agent
Repo Context Doctor scans a repository for the instruction files coding agents read, such as AGENTS.md, CLAUDE.md, Cursor rules, GEMINI.md, Copilot instructions and Windsurf rules, and builds a graph of what each agent inherits. It reports contradictory package-manager, test, lint or build guidance, references to missing files, missing npm run scripts, duplicated directives, context nearing its budget and unsafe guidance. Findings carry paths and line numbers, with output as a human report, JSON, SARIF or Mermaid.
Written by ooruby from the README of repo-context-doctor 0.3.0.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Instruction files that contradict each other or point at missing files change how your coding agent behaves, and this shows where.
What you could do with it
- Run the check command on a repository to list conflicting build and test instructions across agent files.
- Inspect one nested service for a single agent, such as Codex, to see which instructions reach it.
- Export SARIF for pull-request annotations, or a Mermaid graph of how provider files override one another.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
Show the instruction graph your coding agents actually receive.
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.3.0, the file with digest sha512-5NDWkApWjBoFMGWi1HF4/oAq2AW7W9lDaltA/gsdYrGhvuvHTwFc6iJ5FClQORG6HEn+eF8FQ1Z/te3RnnN/gw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y -p repo-context-doctor@0.3.0 repo-context-doctorPinned to 0.3.0, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- repo-context-doctor
- Version read
- 0.3.0
- Resolved
- 2026-10-10
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/repo-context-doctor)About this listing
- Kind
- Agent
- Category
- Developer tools
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from dhait
See the storefrontSimilar agents
All agentsVerification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.