issue-review-reply

Review PigeonPod GitHub issues end to end. Use when the user asks what an issue means, whether it is valid, how to reply, whether to add it to the GitHub Project, or to turn it into a tracked task. Read the issue and comments, inspect relevant local docs and code, explain the real requirement or bug precisely, draft a maintainer reply, and only after explicit approval perform GitHub writes. When creating a task, first recommend `Priority`, `Size`, and `Estimate`, wait for maintainer confirmation or overrides, then write those values into the project task fields.

Quality

100%

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%Weight 40%Scale 1-3

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

The content is dense, actionable, and well-sequenced with explicit approval gates and verification steps; it stays lean while carrying the real project-specific identifiers the task requires. No changes needed.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: concrete gh commands and exact field/option IDs with no concept explanations or padding; every line carries load-bearing specifics Claude cannot infer. Not the level below because there is no unnecessary explanation to tighten.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (e.g. 'gh issue view <number> --json ...', 'gh project item-edit --id ... --field-id ... --single-select-option-id ...') with real field and option IDs, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	A clear six-step sequence with explicit validation checkpoints ('Verify with one of', 'Verify the returned comment URL', 'Always re-read fields before editing') and a hard approval gate ('No explicit approval, no write action'), plus verification after every write — matching the clear-sequence-with-checkpoints anchor.	3 / 3
Progressive Disclosure	No bundle files exist, so the self-contained SKILL.md is scored on organization; it is well-structured into clearly labeled sections (Workflow, Task Recommendation Rules, GitHub Project Rules, Execution Patterns, Output Pattern, Quality Bar) with no nested references. Inline project field IDs are justified as they are needed on every invocation.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and clearly distinguishes this skill's niche; it answers both what it does and when to use it in third-person/imperative voice without fluff. No improvements needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Read the issue and comments, inspect relevant local docs and code, explain the real requirement or bug precisely, draft a maintainer reply... perform GitHub writes... recommend Priority, Size, and Estimate... write those values into the project task fields' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what (review, inspect, explain, draft, write, recommend fields) and when (an explicit 'Use when...' trigger clause), matching the 'clearly answers both what AND when' anchor.	3 / 3
Trigger Term Quality	'Use when the user asks what an issue means, whether it is valid, how to reply, whether to add it to the GitHub Project, or to turn it into a tracked task' covers natural phrasings a maintainer would actually say, matching the good-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'PigeonPod GitHub issues' with triggers tied to project-item and task creation, giving it a clear niche 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: aizhimou/pigeon-pod
Path: .agent/skills/issue-review-reply/SKILL.md
Commit: 27a1e11

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