issue-triage
/issue-triage
Porządkuje zgłoszenia w repozytorium według drzewa decyzji: klasyfikuje, dodaje etykiety i wskazuje brakujące informacje.
- Autor
- stark-ai-de ↗
- Repozytorium
- agent-skills ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 21.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 21.10.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Porządkuje zgłoszenia w repozytorium według drzewa decyzji: klasyfikuje, dodaje etykiety i wskazuje brakujące informacje.
Oryginalny opis (EN)
Triage repository issues through a maintainer decision tree. Use when the user asks to classify issues, apply labels, identify missing information, mark ready-for-agent work, split vague reports, or clean up an issue inbox.
Jak działa
- Goal
- When to use
- When not to use
- Inputs
- Inputs to inspect
- Process
- Workflow
- Decision points
- Safety rules
- References
Podgląd SKILL.md
--- name: issue-triage description: Triage repository issues through a maintainer decision tree. Use when the user asks to classify issues, apply labels, identify missing information, mark ready-for-agent work, split vague reports, or clean up an issue inbox. license: Apache-2.0 metadata: internal: true author: stark-ai-de category: repo-maintenance version: "0.1.0" --- # Issue Triage ## Goal Classify issues into actionable maintainer states, propose labels and responses, and identify what is needed before an agent or human should work on them. ## When to use - The user asks to triage GitHub, GitLab, Linear, or markdown issues. - An inbox needs labels, status, duplicate detection, or missing information checks. - A vague issue needs to be split into smaller work items. ## When not to use - The user asks for implementation rather than issue classification. - The task is reviewing a pull request; use `pr-review`. - The issue appears security-sensitive and should go through private reporting first. ## Inputs - Issue title, body, comments, labels, assignees, linked PRs, and project state. - Repository docs, contribution rules, issue templates, and label conventions. - Live tracker data when the user asks for real issue changes. ## Inputs to inspect - Inspect issue content, linked code/docs, existing labels, and tracker state needed to classify the issue. - Check repository triage conventions before inventing labels. ## Process 1. Read the issue and linked context. 2. Determine category: bug, feature, docs, question, duplicate, wontfix, maintenance, or security. 3. Determine readiness: needs reporter, needs maintainer, ready for agent, ready for human, blocked, or duplicate. 4. Propose labels and a concise maintainer response. 5. Split broad issues into concrete follow-up issues when needed. 6. Ask for approval before applying labels, closing, assigning, or editing issues unless the user explicitly authorized those actions. ## Workflow Use the process above to produce a proposed triage result first. Apply live issue changes only when the user has explicitly authorized that action. ## Decision points - If reproduction steps are missing for a bug, mark `needs-info`. - If expected behavior is a product decision, mark `needs-maintainer`. - If scope and validation are clear, mark `ready-for-agent`. - If the report may be security-sensitive, avoid public detail and escalate to the security policy. ## Safety rules - Do not close or label live issues without approval. - Do not expose security details in public responses. - Do not promise timelines or maintainer commitments. ## References Read only when needed: - `references/triage-state-machine.md` for readiness states. - `references/label-mapping.md` for common labels. ## Scripts No bundled scripts. ## Output format Return: 1. Triage decision 2. Category 3. Readiness state 4. Suggested labels 5. Missing information 6. Draft response 7. Recommended next action ## Failure modes - If issue details are unavailable, ask for the issue body, URL, or tracker access. - If live tracker permissions fail, return the proposed changes as a draft. - If duplicate status is uncertain, name the suspected duplicate and evidence gap. ## Completion criteria - Every issue has a category, readiness state, and next action. - Proposed tracker changes are separated from actions already taken. - Missing information is specific enough for the reporter or maintainer to answer.
Pliki w paczce (3)
- SKILL.md 3 KB
- references/label-mapping.md 1 KB
- references/triage-state-machine.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · stark-ai-de/agent-skills | 90 | Apache-2.0 |
| bentleypark/aiwatch | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| arize-ai/phoenix | 100 | Apache-2.0 |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| mono/SkiaSharp | 100 | MIT |
| arize-ai/coding-harness-tracing | 100 | Apache-2.0 |
| jcdendrite/claude-config | 100 | MIT |
| marcel-bich/marcel-bich-claude-marketplace | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 3b069afec060 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100triage
Porządkuje zgłoszenia według maszyny stanów z rolami triage, od utworzenia po przygotowanie dla agenta. - 100triage
Porządkuje zgłoszenia według maszyny stanów z rolami triage, od tworzenia po przygotowanie dla agenta AFK. - 100github-goal-issue-triage
Segreguje otwarte issues w wielu repozytoriach względem GOAL.md, zakłada etykiety priorytetów p0 do p3, wskazuje następne zadanie i generuje raport HTML. - 100maintainer-triage
Sortuje otwarte zgłoszenia repozytorium GitHub na błędy, funkcje, pytania i duplikaty, a etykiety i odpowiedzi stosuje po potwierdzeniu. - 100triage
Porządkuje zgłoszenia w GitHubie i Jira według ról triage, przygotowuje je dla agenta i zakłada zgłoszenia z planem TDD. - 100github-issue-triage
Przegląda, etykietuje i priorytetyzuje zgłoszenia GitHub, wykrywa duplikaty i nie zmienia nic bez wyraźnej prośby.