القائمة
Use when a GitHub issue backlog needs read-only classification, prioritization, duplicate spotting, or clarification gaps called out.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.
Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub metadata.
Use when a task needs a written execution plan with explicit steps, risks, verification, and user approval before implementation starts.
Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.
Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers.
Use when deciding whether a change is ready to merge and a concise cross-language checklist is more useful than a full narrative review.
| name | triage-issues |
| version | 1.0.0 |
| description | Use when a GitHub issue backlog needs read-only classification, prioritization, duplicate spotting, or clarification gaps called out. |
| activation | {"patterns":["triage.*issues","review.*issues"],"keywords":["issues","triage","backlog"],"max_context_tokens":2500} |
Use this skill for read-only issue analysis.
gh auth status succeedsgh issue list.For each issue, label it as:
Also rate whether it is:
Return:
Use these sections in order: