- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add omagents/omagents --skill github-triage -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add omagents/omagents --skill github-triage -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add omagents/omagents --skill github-triage -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add omagents/omagents --skill github-triage -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/omagents/omagents/tree/HEAD/packages/core/skills/github-triageDe l'éditeur
Systematically review, categorize, and label GitHub issues using a durable task queue. Each issue is processed individually with its result recorded.
By Type: bug, feature, enhancement, documentation, question, duplicate
By Priority: priority:critical, priority:high, priority:medium, priority:low
By Effort: effort:small (<1h), effort:medium (1-4h), effort:large (>4h)
Fetch open issues using the github MCP:
github_list_issues(owner="<owner>", repo="<repo>", state="OPEN", perPage=50)
Initialize the loop with one task per issue:
loop_engine.py init github-triage '[
{"issue_number": 42, "title": "Login fails on Safari", "description": "Triage issue #42: Login fails on Safari"},
{"issue_number": 43, "title": "Add dark mode", "description": "Triage issue #43: Add dark mode"},
{"issue_number": 44, "title": "How to configure X?", "description": "Triage issue #44: How to configure X?"}
]'
Repeat until next returns null:
Step 1: Get next task
loop_engine.py next github-triage
If output is null, go to Phase 3.
Step 2: Read the full issue
github_issue_read(method="get", owner="<owner>", repo="<repo>", issue_number=<N>)
Read the title, body, and existing labels. Read comments if needed.
Step 3: Classify
Determine type, priority, and effort based on the classification reference above.
Step 4: Check for duplicates
github_search_issues(query="repo:<owner>/<repo> is:issue <keywords from title>")
If a duplicate is found, note the original issue number.
Step 5: Apply labels
github_issue_write(
method="update",
owner="<owner>",
repo="<repo>",
issue_number=<N>,
labels=["bug", "priority:high", "effort:medium"]
)
For duplicates, close with a comment:
github_add_issue_comment(
owner="<owner>", repo="<repo>", issue_number=<N>,
body="Closing as duplicate of #<original>. Please follow the original issue for updates."
)
github_issue_write(method="update", owner="<owner>", repo="<repo>", issue_number=<N>, state="closed", state_reason="duplicate")
Step 6: Record result
loop_engine.py complete github-triage <id> "Labeled: bug, priority:high, effort:medium"
If labeling fails (permissions, etc.):
loop_engine.py fail github-triage <id> "Permission denied: cannot label issues"
loop_engine.py summary github-triage
Present the summary table:
| # | Title | Type | Priority | Action |
|---|-------|------|----------|--------|
| 42 | Login fails on Safari | bug | high | Labeled |
| 43 | Add dark mode | feature | medium | Labeled |
| 44 | How to configure X? | question | - | Closed (answered) |
priority:critical - reserve for true blockersTriage GitHub issues using a durable loop workflow. Each issue is classified, labeled, and recorded before moving to the next. Trigger when the user says 'triage issues', 'classify issues', 'organize
---name: github-triagedescription: Triage GitHub issues using a durable loop workflow. Each issue is classified, labeled, and recorded before…---# packages/core/skills/github-triage/SKILL.mdVue d'ensemble
Triage GitHub issues using a durable loop workflow. Each issue is classified, labeled, and recorded before moving to the next. Trigger when the user says 'triage issues', 'classify issues', 'organize issues'.
FAQ
Téléchargez packages/core/skills/github-triage/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/omagents/omagents.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.