do-review-skill

Reviews pull requests that add or modify Agent Skills for structural validity and design quality.

2|Updated May 25, 2026
One-click install
npx skills add https://github.com/edheltzel/Do-Skills --skill do-review-skill-edheltzel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-review-skill
Source: https://github.com/edheltzel/Do-Skills/tree/main/skills/harness/do-review-skill
Command: npx skills add https://github.com/edheltzel/Do-Skills --skill do-review-skill-edheltzel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Reviewing pull requests that add or modify Agent Skills requires checking YAML frontmatter validity, naming conventions, description quality, and marketplace manifest consistency, which is tedious and error-prone when done manually. ## Core Features & Use Cases - Structural Validation: Mechanically verifies YAML frontmatter, required name and description fields, kebab-case naming, line limits, and path formats. - Design and Marketplace Checks: Evaluates description trigger quality, progressive disclosure, degrees of freedom, name collisions, and plugin.json consistency. - Verified Findings Output: Applies a verification protocol to eliminate false positives, then writes severity-calibrated findings (Critical, Major, Minor, Informational) with confidence levels to an output file. - Use Case: When a teammate opens a PR adding a new skill to your marketplace, run this review to automatically flag an invalid frontmatter, a name collision with an existing skill, or a vague description before merge. ## Quick Start Review the skill changes in this PR against the main branch and write the findings to .review-output.md.

Frequently Asked Questions about do-review-skill

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

FAQPage Schema
How do I review a pull request that adds an Agent Skill?▼

Run the review against the PR diff to identify changed skill directories, then it reads each SKILL.md end-to-end and applies structural, design, and marketplace checks. Findings are written to an output file with severity and confidence levels.

What makes a valid SKILL.md file?▼

A valid SKILL.md requires parseable YAML frontmatter with non-empty name and description fields, a kebab-case name under 64 characters, a description under 1024 characters, and a total file length under 500 lines.

Can I change the base branch used for the diff comparison?▼

Yes, pass the --base flag followed by the branch name to compare against. If omitted, the review defaults to comparing against the main branch.

Why does the review flag my skill description as too vague?▼

Descriptions need both a capability statement and trigger conditions so the agent can select the skill accurately among many others. Generic phrases like "helps with code" lack the specific domain terms and activation context needed for reliable triggering.

What happens on a re-review after fixes are applied?▼

Re-reviews only verify that previously flagged issues were addressed correctly and do not introduce new findings. Unfixed Minor items are accepted and not re-flagged, keeping the focus on verification rather than discovery.