triage

Classify GitHub issues, reproduce bugs, and suggest conservative fixes.

30|5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/max-sixty/tend --skill triage-max-sixty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/max-sixty/tend/tree/main/plugins/tend-ci-runner/skills/triage
Command: npx skills add https://github.com/max-sixty/tend --skill triage-max-sixty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triages newly opened GitHub issues by classifying, reproducing bugs, and commenting with conservative fixes.

Core Features & Use Cases

  • Classify new issues by type (Bug report, Feature request, Question, Other).
  • Reproduce and investigate issues using repository context, then suggest fixes.
  • Comment with guidance and load repo-specific skills for targeted triage.

Quick Start

Open a newly created issue and let triage classify it, attempt reproduction if possible, and prepare a comment with a conservative fix.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate GitHub issue triage for newly opened issues in CI?

Automating GitHub issue triage involves classifying new issues by type, checking for duplicates, investigating the codebase to reproduce bugs, and posting maintainer-ready comments with conservative fixes directly within your CI environment.

Can I automatically classify and reproduce bugs from GitHub issues?

Yes, you can automatically classify GitHub issues as bug reports or feature requests and attempt bug reproduction by using repository context and codebase investigation to validate the reported behavior before suggesting fixes.

Does automated issue classification require GitHub CLI access and a CI runner?

Yes, automated issue triage requires GitHub CLI access and a CI context to load repository-specific skills, ensuring the triage workflow can securely interact with issues and apply targeted classification across repositories.

What is the best way to check for duplicate GitHub issues during triage?

The best way to check for duplicate GitHub issues during triage is to use an automated workflow that evaluates newly opened issues against existing repository context to identify and flag potential duplicates before commenting.

How do I post conservative fix suggestions as comments on GitHub issues?

You can post conservative fix suggestions by automating your triage workflow to investigate the codebase, attempt to reproduce the bug, and generate maintainer-ready comments containing the suggested fix directly on the GitHub issue.