gh-compile-issues

Triage N GitHub issues into a coverage matrix: fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence.

Quality

83%

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

100%

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

The body is a lean, highly actionable workflow with executable commands, explicit validation checkpoints, and well-organized sections; it assumes Claude's competence and avoids concept padding.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence — no general explanation of what GitHub issues or git are; every section earns its place with commands, rubrics, and concrete classification rules.	3 / 3
Actionability	Provides executable `gh issue list/view`, `git grep`, `git merge-tree` commands plus exact per-disposition guidance (name the file, function, one-line edit, and proving gate), all copy-paste ready.	3 / 3
Workflow Clarity	A clearly sequenced 7-step workflow with explicit validation checkpoints (`cargo fmt --all -- --check`, `cargo test --workspace --all-features --locked`, `git merge-tree` against the real landing branch) and feedback guidance for error recovery.	3 / 3
Progressive Disclosure	A well-organized single-file skill with clearly labeled sections (Inputs, Workflow, When to use, Credit, Red flags, Output) and no nested references; no bundle files exist, and none are needed for a skill of this size.	3 / 3
	Total	12 / 12 Passed

Description

67%

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

The description is specific and distinct, with concrete actions and a clear niche, but it omits an explicit 'Use when...' trigger and relies on somewhat technical framing rather than natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a maintainer asks to triage a batch of GitHub issues or a whole milestone into a coverage matrix before any action is taken.'

Include natural-language trigger variants users would actually say, such as 'triage issues', 'review a milestone', or 'which issues are already fixed'.

Clarify the 'compile' framing — 'gh-compile-issues' and 'compile' may read as a build/compilation step; rephrase around triage to avoid confusion.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'fetch each, check current code, classify already-done/quick-fix/design/defer with cited evidence' — naming the domain and several specific operations.	3 / 3
Completeness	It clearly states what the skill does but has no explicit 'Use when...' trigger clause; the 'when' is only implied by the task framing, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Mentions 'GitHub issues' and 'coverage matrix' but lacks natural trigger variants a user would say ('triage issues', 'review a milestone', 'which issues are fixed'); the phrase 'compile' is jargon not a natural utterance.	2 / 3
Distinctiveness Conflict Risk	The niche is distinct — triaging a CodeWhale issue set into a coverage matrix with a fixed set of dispositions — unlikely to trigger for unrelated GitHub skills.	3 / 3
	Total	10 / 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: Hmbown/CodeWhale
Path: docs/skills/gh-compile-issues/SKILL.md
Commit: f018d3e

Reviewed: about 13 hours 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.