- Home
- Skills
- Code Quality & Review
- Repository Legibility Review for AI Coding Agents
Repository Legibility Review for AI Coding Agents
Get a prioritized report of repository traps that could cause AI coding agents to make the wrong changes.
Free
Works with the AI Agents you already use
Repository Legibility Review for AI Coding Agents
Example session with this skill installed
Give a compact agent-legibility review of this snapshot: README says tax lives in pricing.ts. pricing.ts exports TAX_RATE=0.2; checkout.ts uses subtotal*1.2 directly. No other files supplied.
- Read your context and instructions
- Compiled the repository legibility review
Reviewed the supplied snapshot for AI-agent edit risks. The main concern is a checkout calculation that appears to repeat the documented tax rule.
Review Summary
Scope: supplied README statement and two code excerpts only. Scores are provisional; consumers, tests, and additional guidance were not inspected.
| Dimension | Score / 5 | Snapshot evidence |
|---|---|---|
| Discoverability | 4 | README points to pricing.ts. |
| Authority visibility | 3 | Named owner exists, but checkout embeds a similar value. |
| Context locality | 3 | Understanding the tax change requires both excerpts. |
| Impact predictability | 2 | Editing TAX_RATE would not update the shown checkout expression. |
| Intent signaling | 3 | TAX_RATE is explicit; checkout's multiplier is not. |
| Hidden knowledge | 3 | The relationship between 0.2 and 1.2 must be inferred. |
Duplicate Concepts
| Priority | Location | Issue and likely mistake | Smallest improvement |
|---|---|---|---|
| P2 | pricing.ts; checkout.ts | If both values represent the same tax policy, an agent following README could update TAX_RATE while leaving checkout unchanged. | Confirm shared meaning, then have checkout use TAX_RATE and add a calculation test. |
The README is useful counter-evidence against missing ownership. It does not explain whether checkout intentionally uses a separate rate. This finding remains conditional on that relationship.
Next steps
- Inspect the complete checkout function and relevant tests.
- Confirm whether both values represent the same tax policy before changing code.
Connects securely to your tools. The creator never sees your data.
About this skill
An AI coding agent can edit the wrong file or miss a business rule that lives elsewhere. This review identifies those traps and gives developers a prioritized list of practical improvements before handing over more coding work.
What it does
- Finds confusing edit paths: Flags places where an agent could struggle to locate the right code.
- Checks sources of truth: Identifies competing definitions and unclear responsibility for business rules.
- Exposes hidden dependencies: Highlights conventions and linked changes that are easy to miss.
- Delivers an actionable report: Includes scores, file references, likely mistakes, and recommended fixes.
- Challenges suspected problems: Checks existing guidance and tests before treating an issue as a finding.
How it works
- Provide access to your repository and request an agent-legibility review.
- Name any common changes you want the review to focus on.
- Receive an evidence-based report with priorities and small, targeted improvements.
- Request implementation separately if you want changes made.
Works with
Repositories across frameworks. Reviews source code, tests, README files, repository guidance, configuration, and generated-code notices.
Why use this skill
It helps you address ambiguity before an agent makes an avoidable mistake. Recommendations focus on clearer edit paths and visible rules, rather than cosmetic cleanup or preferred coding styles.
Use cases
- Prepare a repository for delegated coding tasks.
- Explain rules that new coding agents might miss.
- Prioritize documentation and navigation improvements.
Known limitations
This is not a bug, security, performance, or architecture audit. Large repositories may be sampled, with the review boundary stated.
Source and license
Created by Ray Carter (ruicore). Free and open source under Apache-2.0.
- Canonical source: https://github.com/ruicore/codex-skills/tree/main/skills/agent-legibility-review
- License: https://github.com/ruicore/codex-skills/blob/main/skills/agent-legibility-review/LICENSE
Agensi serves the latest approved marketplace version, which may differ from GitHub main. GitHub changes do not automatically update the marketplace package.
Connect via https://www.agensi.io/mcp and ask for this skill by its published title.
Not a bug, security, performance, or architecture audit. Findings depend on accessible repository evidence; large repositories may be sampled. Code changes require a separate request.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
2 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 23 days ago
- Free with an Agensi account
Permissions
Reads the user-selected repository and project guidance. Review is read-only; changes require a separate user request.