Summary

The coding-standards collection stores its agents and prompts under .github/agents/code-review/ and .github/prompts/code-review/ instead of .github/agents/coding-standards/ and .github/prompts/coding-standards/. This is the only collection that violates the collection-to-folder naming convention. Instructions already use the correct folder (.github/instructions/coding-standards/).

This causes the plugin output to have an inconsistent structure where agents/code-review/ and commands/code-review/ appear alongside instructions/coding-standards/.

Discovery

This discrepancy was discovered during review work on PR #1174 (standards code review agent). The functional-code-review agent was placed in .github/agents/code-review/ before the collection-to-folder naming convention was fully enforced, and was never corrected. PR #1174 adds several more files to the same folder, making now the right time to fix the convention violation on main before that PR can land cleanly.

Files to Move

• .github/agents/code-review/functional-code-review.agent.md → .github/agents/coding-standards/
• .github/prompts/code-review/functional-code-review.prompt.md → .github/prompts/coding-standards/

Path References to Update (8 total)

Auto-Regenerated (via npm run plugin:generate)

• plugins/coding-standards/ — plugin.json, symlinks, README
• plugins/hve-core-all/ — plugin.json, symlinks, README
• extension/README.coding-standards.md and extension/README.hve-core-all.md

Notes

• The code-review tag in coding-standards.collection.yml is retained — it's a valid categorization tag, not a folder name.
• No .github/instructions/code-review/ or .github/skills/code-review/ directories exist on main.

Acceptance Criteria

• No code-review folder paths remain in source-of-truth files
• npm run plugin:generate produces agents/coding-standards/ and commands/coding-standards/
• npm run lint:all passes
• npm run plugin:validate passes