Skip to content

Add structural validation report for .claude/agents catalog - #3117

Open
harshthul wants to merge 1 commit into
ruvnet:mainfrom
harshthul:add-agent-catalog-structural-report
Open

Add structural validation report for .claude/agents catalog#3117
harshthul wants to merge 1 commit into
ruvnet:mainfrom
harshthul:add-agent-catalog-structural-report

Conversation

@harshthul

Copy link
Copy Markdown

Summary

Adds a JSON report from a structural validation pass over the 108 agent definition files under .claude/agents/.

  • 108/108 files valid — every agent .md has a parseable YAML frontmatter block with a non-empty name and description, plus a non-trivial system-prompt body. No LLM calls were made; this is a pure structural/schema check.

  • 11 duplicate agent names found, each defined twice under different paths — mostly a legacy flat file plus a newer categorized copy:

    • code-analyzer, backend-dev, pr-manager, python-specialist, typescript-specialist, tdd-london-swarm, production-validator, goal-planner, sublinear-goal-planner, database-specialist, project-coordinator

    This isn't a parse failure, but it is a real ambiguity — if agents are loaded/resolved by name, it's undefined which of the two definitions actually wins. Full per-name file listing is in the JSON report.

See verification/agent-catalog-structural-report.json for the full per-file report.

Notes for reviewers

  • Scope was intentionally structural-only (no live agent invocation) per the requester's choice — this is meant as a quick catalog-health check, not a functional test of agent behavior.
  • The duplicate-name findings likely warrant a follow-up decision (dedupe, rename, or confirm it's intentional aliasing) but I didn't change any agent files here — this PR only adds the report.

🤖 Generated with Claude Code

Adds a JSON report from a structural validation pass over the 108 agent
definition files under .claude/agents/. All 108 files have valid
frontmatter (name + description) and non-empty system-prompt bodies.

Also surfaces 11 agent names that are defined twice under different
paths (e.g. code-analyzer, backend-dev, pr-manager, python-specialist,
typescript-specialist, tdd-london-swarm, production-validator,
goal-planner, sublinear-goal-planner, database-specialist,
project-coordinator) - mostly a legacy flat file plus a newer
categorized copy. Not a parse failure, but worth a look since it's
ambiguous which definition wins when agents are loaded by name.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@harshthul
harshthul requested a review from ruvnet as a code owner August 28, 2026 04:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant