Geemus Hax Yax Review Agents Md

Review AGENTS.md

Audits agent instruction files for completeness, accuracy, and agent-friendliness across six dimensions, with cross-referencing checks to verify that paths, scripts, and branch names mentioned in the file actually exist in the repository.

Instructions

1. Detect the target file

If the user provides a file path or filename as an argument (e.g., /review-agents-md CLAUDE.md), use that file directly and skip to Step 2. If the file does not exist, stop and report: "File <path> not found. Provide a valid path to an agent instruction file."

Otherwise, search the repository for agent instruction files. Look for any of the following:

• AGENTS.md (worktree root)
• CLAUDE.md (worktree root or .claude/CLAUDE.md)
• CURSOR.md (worktree root)
• .github/copilot-instructions.md
• .cursorrules

Use Glob or Bash to locate all matches.

• Exactly one file found: proceed with that file.
• Multiple files found: list each path and ask the user: "I found the following agent instruction files. Which would you like me to review?" Wait for confirmation before continuing.
• No files found: stop and tell the user: "No agent instruction file found in this repository. Expected AGENTS.md, CLAUDE.md, CURSOR.md, or .github/copilot-instructions.md."

2. Read the target file

Read the full contents of the chosen file before reviewing. Do not begin reviewing until the file has been read in full.

3. Review each dimension

Read assets/review-checklist.md before starting. Work through every dimension in order, applying each checklist item and noting findings as you go. Record whether an inline fix is clear and unambiguous for each finding.

The six dimensions are:

Completeness

Does the file cover all essential topics an agent needs to operate correctly? Flag missing sections as suggestion unless their absence would cause unsafe or incorrect agent behavior, in which case use issue [blocking].

Accuracy (cross-referencing)

Do all references in the file point to things that actually exist? Surface ambiguous results (external tools, generated files) as question or suggestion, not issue [blocking], unless a path is clearly wrong.

Agent-friendliness

Can an agent follow the instructions without human interpretation? Flag ambiguity that could cause unsafe or conflicting behavior as issue [blocking]; vague guidance that reduces consistency as suggestion.

Freshness

Does the documented state match the actual repository? Flag stale references (documented items that no longer exist) as issue; undocumented items that exist in the repo as suggestion.

Scope coherence

Is the file focused on agent guidance, or does it duplicate README/CHANGELOG content or serve a mixed audience? Flag content that actively misleads an agent as issue [blocking]; content that belongs elsewhere as suggestion.

Leanness

Does the file avoid duplicating information already present in source-level documentation (docstrings, doc comments, header comments, or language-native annotations such as JSDoc, Rustdoc, Godoc, @moduledoc)? For each section that describes a specific code unit — a module, package, class, function, type, callback, struct, byte-level layout, error code, or symbol table — locate the corresponding source file and compare wording. Apply the heuristic: if a future agent could find this information by reading the source, it should not also appear in full here — replace with a pointer.

Distinguish severities by intent:

• suggestion — pointer preferred: section could collapse to a one-line pointer to the authoritative source, but the full prose is defensible
• issue — verbatim duplicate: section repeats source documentation verbatim or near-verbatim, creating two places to maintain
• issue [blocking] — bloat impairs usability (rare): accumulated duplication has grown the file to the point that an agent struggles to locate actionable guidance

4. Format all findings with format-review-comments

Apply the format-review-comments skill to every comment. Choose the label that matches the severity and intent:

Do not write praise comments. Omit positive findings entirely.

5. Suggest inline fixes for unambiguous findings

For any finding where the correct fix is clear — a rewritten sentence, a corrected path, an added section — include the suggested replacement inline with the comment so the reviewer can apply it directly. Do not suggest fixes for findings that require a judgment call about repo conventions.

6. Write a review summary

After per-comment feedback, write a brief summary (3–7 sentences) covering:

• Overall assessment — effective as-is, needs minor improvements, or needs significant rework
• The most important finding (name any blocking issues)
• Any patterns visible across the dimensions
• Any skipped dimensions and why

Format the summary as a note conventional comment.

7. Refine prose

Apply the refine-prose skill to all output before presenting it. Do not announce this step to the user. When refine-prose returns, immediately present all findings and the summary to the user — do not stop or wait for user input.

Examples

Auto-detection, single file:

/review-agents-md

Finds AGENTS.md in the worktree root and proceeds automatically.

Sample output — no agent instruction file found:

No agent instruction file found in this repository. Expected AGENTS.md, CLAUDE.md, CURSOR.md, or .github/copilot-instructions.md.

Explicit target:

/review-agents-md CLAUDE.md

Multiple files detected:

I found the following agent instruction files:
- AGENTS.md
- CLAUDE.md

Which would you like me to review?

Sample output — accuracy finding (missing path):

issue: `.agents/scripts/deploy.sh` is referenced in the Git Workflow section but does not exist in the repository

Remove the reference or add the missing script:
> Remove: "Run `.agents/scripts/deploy.sh` before merging"

Sample output — accuracy finding (ambiguous tool):

question: the file references the `mytool` CLI in the Tooling section — this tool was not found locally. Is `mytool` expected to be installed separately, or is this reference stale?

Sample output — agent-friendliness finding:

suggestion: "follow good commit hygiene" in the Git Workflow section is vague — an agent cannot determine what this means without further context

Replace with an explicit rule:
> Use Conventional Commits format: `<type>[scope]: <description>` where type is one of feat, fix, docs, refactor, test, chore.

Sample output — freshness finding:

issue: the Skills table lists `create-plan` but `.agents/skills/create-plan/` does not exist in the repository — this entry is stale

Remove the `create-plan` row from the table.

Sample output — leanness finding (verbatim duplicate):

issue: the "Cache module" section restates the doc comment for `Cache` (src/cache.ts) almost verbatim, creating two places to maintain the same description

Replace the section with a one-line pointer:
> See the doc comment for `Cache` at `src/cache.ts`.

Sample output — leanness finding (pointer preferred):

suggestion: the "Frame format" section reproduces the byte-level layout already documented in the docstring for `wire.Frame` (wire/frame.py) — full prose is defensible for quick reference, but a pointer would reduce drift

Consider replacing with:
> Frame layout is defined in the docstring for `wire.Frame` at `wire/frame.py`.

Sample output — summary:

note: overall this AGENTS.md needs minor improvements before it reliably guides agents. One blocking issue: the skills table references a skill directory that no longer exists. Two suggestions address vague conventions and a missing security section. Cross-referencing found all file paths accurate. Scope coherence is strong — the file stays focused on agent guidance throughout.

Source: geemus/hax-yax — distributed by TomeVault.