gh-file-issue

Use when filing a new CodeWhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

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

A tight, highly actionable filing workflow with executable gh commands, a clear numbered sequence, and explicit validation gates. The only real weakness is hardcoded version/milestone strings (v0.8.62) that are time-sensitive and will decay, slightly denting conciseness.

Suggestions

Move the time-sensitive current milestone/version ('v0.8.62') out of the prose into a clearly marked 'current target' line or a deprecated/old-patterns note so stale values don't rot the body over time.

Have step 5 fetch the live milestone at runtime (the gh api milestones call already exists) rather than hardcoding 'v0.8.62' as 'the current target milestone', eliminating the staleness source entirely.

Trim the opening editorial line ('An issue is maintainer evidence, not a sticky note...') to one clause; it states motivation Claude can infer from the rest of the workflow.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and procedural, but it embeds time-sensitive version numbers inline ('The current target milestone is v0.8.62', title pattern 'v0.8.62: ...') that will go stale and are not isolated in an 'old patterns'/'deprecated' section, plus a little editorial prose ('An issue is maintainer evidence, not a sticky note').	2 / 3
Actionability	Provides fully executable, copy-paste-ready commands (gh issue list/pr list/label list/api milestones, gh issue create with --body-file -, git rev-parse, grep -rn) and a concrete title pattern with a worked example, matching the fully-executable anchor.	3 / 3
Workflow Clarity	A clearly sequenced 7-step workflow with explicit pre-flight validation — 'Confirm the code claim from source, never from memory', 'Check for duplicates', and the falsifiable-acceptance-criteria readiness gate ('If you cannot state how it's verified, the issue is not ready') — plus a Red flags checklist.	3 / 3
Progressive Disclosure	No bundle files exist and none are needed; the body is self-contained with well-organized sections (When to use, Workflow, Red flags, Output), so the well-organized-sections condition for a reference-free single-purpose skill is met.	3 / 3
	Total	11 / 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.

A concise, well-constructed description that explicitly states the trigger, the concrete deliverables (repro, acceptance criteria, labels, milestone), and a distinct niche. It scores at the top of the scale on all four dimensions with no vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions and components — 'turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone' — matching the anchor that lists several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone') and when ('Use when filing a new CodeWhale GitHub issue'), satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Includes natural terms a user would say for this niche — 'filing a new CodeWhale GitHub issue', 'bug or idea', 'issue' — giving good coverage of the phrasings that would surface this skill.	3 / 3
Distinctiveness Conflict Risk	The CodeWhale-specific GitHub-issue-filing niche with explicit triggers ('filing a new CodeWhale GitHub issue') is a clear, distinct slot unlikely to fire for unrelated skills.	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: Hmbown/CodeWhale
Path: docs/skills/gh-file-issue/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.