--- name: issue-triage-d30641559e5f description: > Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French. allowed-tools: - Bash - Read - Grep effort: medium tags: [triage, issues, github, categorize, duplicates, risk] --- # Issue Triage ## Quand utiliser | Skill | Usage | Output | |-------|-------|--------| | `/issue-triage` | Trier, analyser, commenter les issues | Tableaux d'action + deep analysis + commentaires postés | | `/repo-recap` | Récap général pour partager avec l'équipe | Résumé Markdown (PRs + issues + releases) | **Déclencheurs** : - Manuellement : `/issue-triage` ou `/issue-triage all` ou `/issue-triage 42 57` - Proactivement : quand >10 issues ouvertes sans triage, ou issue stale >30j détectée --- ## Langue - Vérifier l'argument passé au skill - Si `en` ou `english` → tableaux et résumé en anglais - Si `fr`, `french`, ou pas d'argument → français (défaut) - Note : les commentaires GitHub (Phase 3) restent TOUJOURS en anglais (audience internationale) --- Workflow en 3 phases : audit automatique → deep analysis opt-in → commentaires avec validation obligatoire. ## Préconditions ```bash git rev-parse --is-inside-work-tree gh auth status ``` Si l'un échoue, stop et expliquer ce qui manque. --- ## Phase 1 — Audit (toujours exécutée) ### Data Gathering (commandes en parallèle) ```bash # Identité du repo gh repo view --json nameWithOwner -q .nameWithOwner # Issues ouvertes avec métadonnées complètes gh issue list --state open --limit 100 \ --json number,title,author,createdAt,updatedAt,labels,assignees,body,comments # PRs ouvertes (pour cross-référence) gh pr list --state open --limit 50 --json number,title,body # Issues fermées récemment (pour détection doublons) gh issue list --state closed --limit 20 \ --json number,title,labels,closedAt # Collaborateurs (pour protéger les issues des mainteneurs) gh api "repos/{owner}/{repo}/collaborators" --jq '.[].login' ``` **Fallback collaborateurs** : si `gh api .../collaborators` échoue (403/404) : ```bash gh pr list --state merged --limit 10 --json author --jq '.[].author.login' | sort -u ``` Si toujours ambigu, demander à l'utilisateur via `AskUserQuestion`. **Note** : `author` est un objet `{login: "..."}` — toujours extraire `.author.login`. ### Analyse — 6 dimensions **1. Catégorisation** (labels existants > inférence titre/body) : - **Bug** : mots-clés `crash`, `error`, `fail`, `broken`, `regression`, `wrong`, `unexpected` - **Feature** : `add`, `implement`, `support`, `new`, `feat:` - **Enhancement** : `improve`, `optimize`, `better`, `enhance`, `refactor` - **Question/Support** : `how`, `why`, `help`, `unclear`, `docs`, `documentation` - **Duplicate Candidate** : voir dimension 3 ci-dessous **2. Cross-ref PRs** : - Scanner `body` de chaque PR ouverte pour `fixes #N`, `closes #N`, `resolves #N` (case-insensitive, regex) - Construire un map : `issue_number -> [PR numbers]` - Une issue liée à une PR mergée → recommander fermeture **3. Détection doublons** : - Normaliser les titres : lowercase, strip préfixes (`bug:`, `feat:`, `[bug]`, `[feature]`, etc.) - **Jaccard sur mots des titres** : si score > 60% entre deux issues → candidat doublon - **Keywords body overlap** > 50% → renforcement du signal - Comparer aussi avec issues fermées récentes (20 dernières) - Un faux positif peut être confirmé/écarté en Phase 2 **4. Classification risque** : - **Rouge** : mots-clés `CVE`, `vulnerability`, `injection`, `auth bypass`, `security`, `exploit`, `unsafe`, `credentials`, `leak`, `RCE`, `XSS` - **Jaune** : `breaking change`, `migration`, `deprecation`, `remove API`, `breaking`, `incompatible` - **Vert** : tout le reste **5. Staleness** : - >30j sans activité (updatedAt) → **Stale** - >90j sans activité → **Very Stale** - Calculer depuis la date actuelle **6. Recommandations d'action** : - `Accept & Prioritize` : issue claire, reproducible, dans scope - `Label needed` : issue sans label - `Comment needed` : info manquante, body insuffisant - `Linked to PR` : une PR ouverte référence cette issue - `Duplicate candidate` : candidat doublon identifié (préciser avec `#N`) - `Close candidate` : stale + aucune activité récente, ou hors scope (jamais si auteur est collaborateur) - `PR merged → close` : PR liée est mergée, issue encore ouverte ### Output — 5 tableaux ``` ## Issues ouvertes ({count}) ### Critiques (risque rouge) | # | Titre | Auteur | Âge | Labels | Action | | - | ----- | ------ | --- | ------ | ------ | ### Liées à une PR | # | Titre | Auteur | PR(s) liée(s) | Status PR | Action | | - | ----- | ------ | ------------- | --------- | ------ | ### Actives | # | Titre | Auteur | Catégorie | Âge | Labels | Action | | - | ----- | ------ | --------- | --- | ------ | ------ | ### Doublons candidats | # | Titre | Doublon de | Similarité | Action | | - | ----- | ---------- | ---------- | ------ | ### Stale | # | Titre | Auteur | Dernière activité | Action | | - | ----- | ------ | ----------------- | ------ | ### Résumé - Total : {N} issues ouvertes - Critiques : {N} (risque sécurité ou breaking) - Liées à PR : {N} - Doublons candidats : {N} - Stale (>30j) : {N} | Very Stale (>90j) : {N} - Sans labels : {N} - Quick wins (à fermer ou labeler rapidement) : {liste} ``` 0 issues → afficher `Aucune issue ouverte.` et terminer. **Note** : `Âge` = jours depuis `createdAt`, format `{N}j`. Si >30j, afficher en **gras**. ### Copie automatique Après affichage du tableau de triage, copier dans le presse-papier : ```bash # Cross-platform clipboard clip() { if command -v pbcopy &>/dev/null; then pbcopy elif command -v xclip &>/dev/null; then xclip -selection clipboard elif command -v wl-copy &>/dev/null; then wl-copy else cat fi } clip <<'EOF' {tableau de triage complet} EOF ``` Confirmer : `Tableau copié dans le presse-papier.` (FR) / `Triage table copied to clipboard.` (EN) --- ## Phase 2 — Deep Analysis (opt-in) ### Sélection des issues **Si argument passé** : - `"all"` → toutes les issues ouvertes - Numéros (`"42 57"`) → uniquement ces issues - Pas d'argument → proposer via `AskUserQuestion` **Si pas d'argument**, afficher : ``` question: "Quelles issues voulez-vous analyser en profondeur ?" header: "Deep Analysis" multiSelect: true options: - label: "Toutes ({N} issues)" description: "Analyse approfondie de toutes les issues avec agents en parallèle" - label: "Critiques uniquement" description: "Focus sur les {M} issues à risque rouge/jaune" - label: "Doublons candidats" description: "Confirmer ou écarter les {K} doublons détectés" - label: "Stale uniquement" description: "Décision close/keep sur les {J} issues stale" - label: "Passer" description: "Terminer ici — juste l'audit" ``` Si "Passer" → fin du workflow. ### Exécution de l'analyse Pour chaque issue sélectionnée, lancer un agent via **Task tool en parallèle** : ``` subagent_type: general-purpose model: sonnet prompt: | Analyze GitHub issue #{num}: "{title}" by @{author} **Metadata**: Created {createdAt}, last updated {updatedAt}, labels: {labels} **Body**: {body} **Existing comments** ({comments_count} total, showing last 5): {last_5_comments} **Context**: - Linked PRs: {linked_prs or "none"} - Duplicate candidate of: {duplicate_of or "none"} - Risk classification: {risk_color} Analyze this issue and return a structured report: ### Scope Assessment What is this issue actually asking for? Is it clearly defined? ### Missing Information What's needed to act on this? (reproduction steps, version, environment, etc.) ### Risk & Impact Security risk? Breaking change? Who's affected? ### Effort Estimate XS (<1h) / S (1-4h) / M (1-2d) / L (3-5d) / XL (>1 week) ### Priority P0 (critical, act now) / P1 (high, this sprint) / P2 (medium, backlog) / P3 (low, someday) ### Recommended Action One of: Accept & Prioritize, Request More Info, Mark Duplicate (#N), Close (Stale), Close (Out of Scope), Link to Existing PR ### Draft Comment Draft a GitHub comment in English using the appropriate template from templates/issue-comment.md. Be specific, helpful, and constructive. ``` Si issue a >50 commentaires, résumer les 5 derniers uniquement. Agréger tous les rapports. Afficher un résumé après toutes les analyses. --- ## Phase 3 — Actions (validation obligatoire) ### Types d'actions possibles - **Commenter** : `gh issue comment {num} --body-file -` - **Labeler** : `gh issue edit {num} --add-label "{label}"` (skip si label déjà présent) - **Fermer** : `gh issue close {num} --reason "not planned"` (jamais sans validation) ### Génération des drafts Pour chaque issue analysée, générer les actions (commentaire + labels + fermeture si applicable) en utilisant `templates/issue-comment.md`. **Règles** : - Langue des commentaires : **anglais** (audience internationale) - Ton : professionnel, constructif, factuel - Ne jamais re-labeler une issue qui a déjà ce label - Ne jamais proposer "close" pour une issue d'un collaborateur - Toujours afficher le draft AVANT tout `gh issue comment` ### Affichage et validation **Afficher TOUS les drafts** au format : ``` --- ### Draft — Issue #{num}: {title} **Actions proposées** : {Commentaire | Label: "bug" | Fermeture} **Commentaire** : {commentaire complet} --- ``` Puis demander validation via `AskUserQuestion` : ``` question: "Ces actions sont prêtes. Lesquelles voulez-vous exécuter ?" header: "Exécuter" multiSelect: true options: - label: "Toutes ({N} actions)" description: "Commenter + labeler + fermer selon les drafts" - label: "Issue #{x} — {title_truncated}" description: "Exécuter uniquement les actions pour cette issue" - label: "Aucune" description: "Annuler — ne rien faire" ``` (Générer une option par issue + "Toutes" + "Aucune") ### Exécution Pour chaque action validée, exécuter dans l'ordre : commenter → labeler → fermer. ```bash # Commenter gh issue comment {num} --body-file - <<'COMMENT_EOF' {commentaire} COMMENT_EOF # Labeler (si applicable) gh issue edit {num} --add-label "{label}" # Fermer (si applicable) gh issue close {num} --reason "not planned" ``` Confirmer chaque action : `Commentaire posté sur issue #{num}: {title}` Si "Aucune" → `Aucune action exécutée. Workflow terminé.` --- ## Gestion des cas limites | Situation | Comportement | |-----------|--------------| | 0 issues ouvertes | `Aucune issue ouverte.` + terminer | | Issue sans body | Catégoriser par titre, recommander `Comment needed` | | >50 commentaires | Résumer les 5 derniers uniquement | | Faux positif doublon | Phase 2 confirme/écarte — ne pas agir sur suspicion seule | | Labels déjà présents | Ne pas re-labeler, signaler "label déjà appliqué" | | Issue d'un collaborateur | Jamais `close candidate` automatique | | Rate limit GitHub API | Réduire `--limit`, notifier l'utilisateur | | PR mergée liée à issue ouverte | Recommander fermeture de l'issue | | Issue sans activité >90j | Very Stale — proposer fermeture avec message bienveillant | | Duplicate confirmed in Phase 2 | Poster commentaire + fermer en faveur de l'issue originale | --- ## Notes - Toujours dériver owner/repo via `gh repo view`, jamais hardcoder - Utiliser `gh` CLI (pas `curl` GitHub API) sauf pour la liste des collaborateurs - `updatedAt` peut être null sur certaines issues → traiter comme `createdAt` - Ne jamais poster ou fermer sans validation explicite de l'utilisateur dans le chat - Les commentaires draftés doivent être visibles AVANT tout `gh issue comment` - Similarité Jaccard = |intersection mots| / |union mots| (exclure stop words : a, the, is, in, of, for, to, with, on, at, by) --- Source attribution: roberttmadsen13-del Original project: https://github.com/roberttmadsen13-del/TOURney/blob/887b95224dcc4b9c0a60f25230c5faa7105a4d1f/SKILLS/rtk-master/.claude/skills/issue-triage/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS Copyright 2024 rtk-ai and rtk-ai Labs Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: roberttmadsen13-del Original project: https://github.com/roberttmadsen13-del/TOURney/blob/887b95224dcc4b9c0a60f25230c5faa7105a4d1f/SKILLS/rtk-master/.claude/skills/issue-triage/SKILL.md Attribution basis: Source repository record Fields of work: Content & Media, Development & Engineering, Product Management, Sales Roles: Backend Developer, Product Manager, QA / Test Engineer, Sales Development Rep (SDR), Technical Writer Specialties: API, Backend Tools: GitHub, Bash Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 90610b5503c90a0a18c0505b5f1417a24db0cd6e43f4ba438a733f51a8b1290c