issue-review

Reviews a GitHub issue to determine validity, classify as user error or bug, check if already fixed, and take appropriate action. For user errors, improves error messages and documentation. For real bugs, implements a fix following the full commit workflow including tests and adversarial review. Closes the issue with a clear resolution message. Use when the user says "review issue", "triage issue", "is this a bug", "check issue", "issue review", or provides a GitHub issue URL or number.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-5

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

A highly actionable, well-sequenced workflow with strong validation and feedback loops. The main weakness is monolithic structure: the lengthy closing-comment templates and reference-style detail could be split into bundled reference files for better progressive disclosure.

Suggestions

Move the six Step 8 closing-comment templates into a bundled reference file (e.g. references/closing-comments.md) and link to it from Step 8, keeping only one short example inline.

Consider extracting the classification routing tables (Steps 2c and 3c) into a reference file so SKILL.md reads as a concise overview.

Tighten the Notes section by merging near-duplicate guidance (e.g. the 'multiple problems' and 'multiple modules' bullets) to reduce token weight.

Dimension	Reasoning	Score
Conciseness	Per-section content is lean and actionable, but the six full heredoc closing-comment templates (Steps 8) add notable length that could be condensed; slightly above the verbose midpoint.	4 / 5
Actionability	Concrete, copy-paste-ready `gh`/`git`/`mvn` commands, classification routing tables, commit-message templates, and closing-comment templates cover the common cases fully.	5 / 5
Workflow Clarity	A clear 8-step sequence with routing tables, a decision flowchart, explicit validation (run tests, adversarial review), feedback loops (test→fix→retest, BLOCK→fix→re-review), and a user-approval GATE before closing.	5 / 5
Progressive Disclosure	Well-structured with headers, tables, and a flowchart, but it is a single ~520-line monolithic file with the verbose closing templates inlined and no skill-level reference files to split detail into.	3 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

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

A strong, third-person description that clearly states what the skill does and when to invoke it, with concrete trigger phrases and a distinct niche. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'determine validity, classify as user error or bug, check if already fixed', 'improves error messages and documentation', 'implements a fix following the full commit workflow including tests and adversarial review', 'Closes the issue with a clear resolution message' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' (review, classify, act, close) and 'when' via a concrete 'Use when the user says…' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Provides natural trigger phrases users would say — "review issue", "triage issue", "is this a bug", "check issue", "issue review" — plus the GitHub issue URL or number variant, covering synonyms and input shapes.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear GitHub-issue-triage niche with distinct triggers and an explicit repo/URL pattern, minimizing overlap with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (533 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: mock-server/mockserver-monorepo
Path: .opencode/skills/issue-review/SKILL.md
Commit: 817ee95

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.