om-code-review

Reviews diffs, branches, and PRs against correctness, security, and breaking-change checklists with severity-ranked findings.

2.6k|159|Updated Mar 8, 2021
One-click install
npx skills add https://github.com/go-musicfox/go-musicfox --skill om-code-review-go-musicfox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: om-code-review
Source: https://github.com/go-musicfox/go-musicfox/tree/main/.agents/skills/om-code-review
Command: npx skills add https://github.com/go-musicfox/go-musicfox --skill om-code-review-go-musicfox

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing code changes consistently is hard: reviewers miss security holes, breaking contract changes, and failing validation gates, and review quality varies from person to person. This Skill standardizes code review by running the repository's configured validation commands, applying a built-in staff-engineer checklist plus any repo-local rules, and producing a structured, severity-ranked report with a clear approve or request-changes verdict. ## Core Features & Use Cases - Mandatory validation gate: Runs every command in the repo's validation.commands config in order and treats any failure as a blocker finding, so the review mirrors what CI will do. - Layered checklists: Applies a built-in checklist covering correctness, security, breaking changes, tests, concurrency, performance, and dependencies, extended by repo-local CODE_REVIEW.md, BACKWARD_COMPATIBILITY.md, and configured checklist files. - Structured verdict report: Produces a human-readable report with a validation-gate table, findings grouped by blocker/major/minor/nit severity with file and line references, a breaking-change checklist, and a mechanical approve/request-changes verdict. - Use Case: Point it at a pull request number before merging; it fetches the diff via tracker operations, runs the test and lint gates, flags a missing permission check as a blocker, and posts a full review report that maintainers can act on directly. ## Quick Start Ask the agent to review the current branch's changes against the base branch and produce a severity-ranked code review report with a merge verdict.

Frequently Asked Questions about om-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request automatically before merging?

Provide a PR number and the review fetches the diff via tracker operations, runs the repository's configured validation commands, applies the built-in and repo-local checklists, and returns a severity-ranked report with an approve or request-changes verdict.

How does automated code review detect breaking changes?

Every changed file is checked against contract surfaces: exported APIs, HTTP routes and response shapes, event names, CLI flags, database schema, and config formats. Removing or renaming any surface without a deprecation path is flagged as a blocker.

Can I add repo-specific review rules to the checklist?

Yes. Set a reviewChecklist path in .ai/agentic.config.json or add CODE_REVIEW.md at the repo root; these extend the built-in checklist. BACKWARD_COMPATIBILITY.md is also enforced when present, with violations flagged as critical.

What happens when a validation gate command fails during review?

Any failing validation command becomes a blocker finding regardless of whose change caused it, and the verdict becomes request changes. The report includes a table showing the actual pass or fail result of every configured command.

Does the review skill modify code or post labels itself?

No. It is a read-only review engine that produces the report and verdict. Caller skills own label transitions, claim protocols, and posting the report as the PR review body.