issue-review

Route GitHub issue reviews to downstream skills via triage rules.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/michael-conrad/.opencode --skill issue-review-michael-conrad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-review
Source: https://github.com/michael-conrad/.opencode/tree/main/skills/issue-review
Command: npx skills add https://github.com/michael-conrad/.opencode --skill issue-review-michael-conrad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified orchestration of GitHub issue reviews to ensure comprehensive data gathering, correct path classification, and safe delegation to downstream skills.

Core Features & Use Cases

  • Gather issue data from the body and all comments to establish context.
  • Classify the appropriate review path (audit, analyze-and-spec, qa, just-review, or already-handled) based on content signals.
  • Route tasks to downstream skills with precise context and governance.
  • Maintain durable exec summaries and compliance with policy gates; avoid unsafe actions on GitHub.

Quick Start

Start the issue-review workflow on a target GitHub issue to collect context, determine routing, and dispatch tasks to downstream skills.

Frequently Asked Questions about issue-review

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

FAQPage Schema
How do I automate GitHub issue triage and routing for my repository?

Automating GitHub issue triage involves gathering the issue body and comments to establish context, then applying triage rules to classify the review path and route tasks to downstream skills for execution.

What is the best way to orchestrate GitHub issue reviews across multiple workflows?

Orchestrating GitHub issue reviews requires a unified task flow that gathers issue data, applies content analysis to determine the correct path, and safely delegates to downstream skills like audit or qa.

Can I route GitHub issues to different analysis tasks based on their content?

Yes, routing GitHub issues based on content allows you to classify the appropriate review path—such as analyze-and-spec, audit, or qa—and dispatch tasks to the corresponding downstream skills with precise context.

How do I start a GitHub issue review workflow?

To start a GitHub issue review workflow, target a specific issue to collect context from its body and comments, determine the appropriate routing path, and dispatch tasks to downstream skills.

Does the issue review orchestration process support safe delegation without unsafe GitHub actions?

Yes, issue review orchestration maintains durable execution summaries and compliance with policy gates to ensure safe delegation to downstream skills while avoiding unsafe actions on GitHub.

What downstream paths can a GitHub issue be classified into during triage?

During GitHub issue triage, content signals classify the issue into paths like audit, analyze-and-spec, qa, just-review, or already-handled to determine the correct downstream skill routing.