`/code-review` isn't firm enough about having to read CODING_STANDARDS.md

On several instances /code-review has simply ignored reading the CODING_STANDARDS.md file and thus the whole code review flow failed to actually follow the coding standards. Here's how Fable 5.1 itself put it

My fault, not the reviewer's. The skill says to find "anything in the repo that documents how code should be written, such as CODING_STANDARDS.md or CONTRIBUTING.md" — I listed standards files from memory of what I'd already read (AGENTS.md, app/AGENTS.md, docs/frontend-coding-conventions.md, app/src/README.md) instead of searching for them. CODING_STANDARDS.md sits at the repo root and is the file with the Comments rules, and nothing in AGENTS.md links to it, so the sub-agent was never given the one document that would have flagged this. It reported against the rules I handed it and found the Props naming breach in app/src/README.md — which is exactly what it was pointed at.

Likely the skill needs firmer language (e.g. "If CODING_STANDARDS.md or CONTRIBUTING.md exist in the repo root it must be provided to the standards reviewer sub-agent.").