veomni-review

Use this skill before committing ANY code change — this is a mandatory gate in the commit flow. Also trigger proactively when: you've made changes across multiple files and want to check consistency, you're unsure if a fix is safe, a change touches shared infrastructure (BaseTrainer, distributed, model loading, data pipeline), or a change is larger than a few lines. The review launches a subagent that checks implementation quality, multi-file consistency, and known constraint violations, then rates the change as safe/needs-attention/risky.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a tight, actionable workflow with concrete commands, a ready-to-use subagent prompt, clear sequencing, and validation checkpoints. It is well-organized and respects Claude's intelligence without unnecessary explanation.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain basic concepts, and every section (steps, subagent prompt template, verdict table) earns its place without padding.	3 / 3
Actionability	It provides concrete, executable guidance — specific commands like `git diff` and `make quality`, a fully copy-paste-ready subagent prompt template, and a verdict-to-action table with clear next steps.	3 / 3
Workflow Clarity	The 1–5 step sequence is clearly ordered with explicit validation checkpoints (`make quality`), a verdict-table feedback loop that gates committing, and an embedded review checklist for the subagent.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is appropriately self-contained; it is well-organized into clearly labeled sections (Steps, Subagent Launch, After Commit) with no nested or multi-level references to navigate.	3 / 3
	Total	12 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong, well-constructed description that explicitly states what the skill does and when to use it, with concrete actions and natural trigger terms. It avoids vague fluff and uses appropriate third-person voice throughout.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — it 'launches a subagent that checks implementation quality, multi-file consistency, and known constraint violations, then rates the change as safe/needs-attention/risky', matching the anchor for several specific actions rather than vague language.	3 / 3
Completeness	It explicitly answers both 'what' (subagent checks and verdict ratings) and 'when' ('Use this skill before committing ANY code change' plus 'Also trigger proactively when:'), with explicit trigger guidance and third-person voice, so it is not capped at 2.	3 / 3
Trigger Term Quality	It uses natural phrases a developer would actually say — 'before committing ANY code change', 'made changes across multiple files', 'unsure if a fix is safe', 'larger than a few lines' — giving good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche — a mandatory pre-commit review gate for the VeOmni framework — with distinct triggers unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ByteDance-Seed/VeOmni
Path: .agents/skills/veomni-review/SKILL.md
Commit: 9ff4858

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.