Code Review

Validate SKILL.md frontmatter, sections, and cross-references for repository standards.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/NEXUZ-SYS/devflow --skill code-review-nexuz-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Code Review
Source: https://github.com/NEXUZ-SYS/devflow/tree/main/.context/skills/code-review
Command: npx skills add https://github.com/NEXUZ-SYS/devflow --skill code-review-nexuz-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps maintain high-quality, consistent skill units by validating frontmatter, sections, and cross-references in SKILL.md and related files, ensuring alignment with repository standards and dotcontext v2 compliance.

Core Features & Use Cases

  • Frontmatter validation: type, name, description, status, scaffoldVersion are present and correctly formatted.
  • Structure and references: required sections count, valid cross-references, kebab-case naming, and alignment with references/skills-map.
  • Change management: detects updates to SKILL.md, agent playbooks, and hooks, and provides actionable feedback for improvements.

Quick Start

Review the latest SKILL.md and associated files to verify frontmatter and references.

Frequently Asked Questions about Code Review

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

FAQPage Schema
What is the best way to enforce kebab-case naming and cross-references across a skills repository?

This skill enforces consistent skill metadata by validating frontmatter completeness, checking required sections, verifying cross-references exist, enforcing kebab-case naming, and flagging unsafe content in SKILL.md files.

Can I use code review automation to detect unsafe content in skill metadata?

To check for non-breaking changes when updating SKILL.md, this skill detects modifications to associated files and agent playbooks, comparing them against repository standards to provide actionable feedback for improvements.

Why does my SKILL.md frontmatter fail repository quality assurance?

Your SKILL.md frontmatter fails quality assurance because required metadata fields are missing or incorrectly formatted, or because cross-references and structural sections do not align with scaffoldVersion and dotcontext v2 compliance.

Do I need dependencies to validate skill metadata and structure?

You do not need external dependencies to validate skill metadata and structure, as this skill operates independently to enforce frontmatter completeness, naming conventions, and structural alignment across the repository.