code-review

Two-axis review of the diff between HEAD and a fixed point the user supplies:

• Standards: does the code conform to this repo's documented coding standards?
• Spec: does the code faithfully implement the originating issue / spec?

Both axes run as parallel sub-agents so they don't pollute each other's context, then this skill aggregates their findings.

Output contract

The review has one substance contract across runtimes. Report the separate ## Standards and ## Spec axes, and write every finding as ordinary Markdown with its file and exact line or tight line range. Keep the Markdown findings in the review so the result remains readable outside a review UI.

The presentation layer may add runtime metadata, but it does not change the finding set. On Codex, follow the platform translation for actionable findings that belong to a changed line; on Claude, use the Markdown finding alone.