skills.rest
Cohey0727
Cohey0727COMMUNITY
Explore all skills by this author →
GitHub

dev-issue-review

Reviews GitHub issues for validity, verifies claims against the codebase, and applies labels.

Updated Jun 28, 2026
Search Tags:#automation#github#gh cli#triage#labeling#issue review#codebase verification
One-click install
npx skills add https://github.com/Cohey0727/CodingAgentTools --skill dev-issue-review-cohey0727
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-issue-review
Source: https://github.com/Cohey0727/CodingAgentTools/tree/main/skills/dev-issue-review
Command: npx skills add https://github.com/Cohey0727/CodingAgentTools --skill dev-issue-review-cohey0727

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Development issues often contain inaccurate file paths, outdated assumptions, or misaligned designs. This Skill automates the triage of open GitHub issues by validating their content against the actual repository, correcting the body, and applying review status labels. ## Core Features & Use Cases - Automated Issue Selection: Finds the oldest unreviewed open issue via the GitHub CLI, skipping ones already labeled in-review, WIP, or needs-info. - Validity Verification: Checks issue claims against the latest main branch and supplements uncertain technical decisions with web research citing source URLs. - Label-Based Workflow: Applies in-review, reviewed, or needs-info labels to prevent duplicate reviews and route issues needing user decisions. - Use Case: Run it in a repository with a backlog of untriaged issues to have each one fact-checked against the codebase, corrected in place, and marked reviewed or escalated with questions. ## Quick Start Ask the AI to review the open issues in this repository and label the valid ones as reviewed.

Frequently Asked Questions about dev-issue-review

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

FAQPage Schema
How do I automatically review GitHub issues for validity?▼

Use the GitHub CLI to list open issues without reviewed, in-review, WIP, or needs-info labels, then verify each issue's claims against the latest main branch. Valid issues get corrected bodies and a reviewed label; unclear ones get needs-info.

How to triage a backlog of open GitHub issues with gh CLI?▼

Run gh issue list with a JSON filter excluding already-labeled issues, sorted by creation date, and process the oldest first. The gh issue view, edit, comment, and close commands handle inspection, correction, and resolution.

Can this review issues that are already being worked on?▼

No. Issues labeled in-review or WIP are skipped to prevent duplicate reviews and interference with active implementation. Explicitly passing such an issue number still results in a skip with a report.

What happens when an issue needs a user decision?▼

The reviewer adds a needs-info label with a comment listing the open questions, removing in-review. After the user answers, re-running the review on that issue number resumes the normal judgment flow.

When does the review close an issue instead of approving it?▼

An issue is closed only when it is clearly unrelated to the repository's purpose, already implemented or resolved, or technically impossible with no alternative. Ambiguous cases are held with needs-info instead of closing.

Related Skills

Explore More Software Engineering Skills→
lucasilverentandlucasilverentand
3

analyze-issue

Validate issue file references and assess claim quality against the codebase.

Community
Intermediate
nbramianbramia
20

implement

Coordinate end-to-end implementation workflows from issue understanding through PR merge.

Community
Advanced
decebalsdecebals
725

issue-triage

Categorize, prioritize, and respond to GitHub issues for Java projects.

Community
Intermediate
CommunityToolkitCommunityToolkit
622

external-comms

Drafts GitHub issue and discussion responses with mandatory human review before posting.

Official
Advanced