Skills issue-triage

📦

issue-triage

Name: issue-triage
Author: yunshu0909

Content revision r1 Safe ⚙️ External commands

Triage GitHub Issues With Clear Replies

Maintainers often need to understand issue reports before they answer. This skill guides Claude, Codex, or Claude Code through diagnosis, classification, decision support, and reply drafting.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "issue-triage" from https://skillstore.io/skills/yunshu0909-issue-triage.md and its manifest at https://skillstore.io/api/skills/yunshu0909-issue-triage/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/yunshu0909-issue-triage.md Signed manifest GET /api/skills/yunshu0909-issue-triage/manifest Signed lockfile GET /api/skills/yunshu0909-issue-triage/lockfile

Test it

Using "issue-triage". A user reports that a setting is ignored after restart.

Expected outcome:

The report is treated as a likely bug. The response explains the affected setting, the suspected persistence path, the files to inspect, and a request for version details.

Using "issue-triage". A user asks for a workflow the product was not designed to support.

Expected outcome:

The issue is classified as an architecture limit or feature request. The reply explains the design boundary, available workaround, estimated implementation cost, and possible future direction.

Using "issue-triage". A maintainer needs to answer a frustrated user professionally.

Expected outcome:

The draft thanks the user, avoids blame, summarizes the finding, gives concrete next steps, and asks for confirmation before posting.

Security Audit

Safe

v5 • 7/8/2026 Open versioned report

All static findings are false positives caused by Markdown inline code or code fences, not executable Ruby or shell backticks. The skill is readable Markdown with no obfuscated payload, prompt injection, or suspicious hidden intent found.

Files scanned

159

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (3)

SKILL.md:23 SKILL.md:108-119 SKILL.md:119-131

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/yunshu0909-issue-triage/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/yunshu0909-issue-triage/security.svg)](https://skillstore.io/skills/yunshu0909-issue-triage?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/yunshu0909-issue-triage?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/yunshu0909-issue-triage/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/yunshu0909-issue-triage.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

yunshu0909. (2026). issue-triage security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/yunshu0909-issue-triage/audits/5

BibTeX citation

@techreport{yunshu0909-yunshu0909-issue-triage-2026,
  author = {yunshu0909},
  title = {issue-triage security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/yunshu0909-issue-triage/audits/5},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "issue-triage security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
  - name: "yunshu0909"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/yunshu0909-issue-triage/audits/5"
identifiers:
  - type: other
    value: "skillstore:yunshu0909-issue-triage:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Handle bug reports

Trace reported behavior through the codebase, identify likely causes, and prepare a clear maintainer response.

Review feature requests

Separate new capability requests from defects, estimate implementation cost, and explain product tradeoffs.

Support repository users

Turn incomplete user reports into structured questions, workaround guidance, and polite follow-up replies.

Try These Prompts

Summarize an issue

Use this skill to read the GitHub issue I provide. Summarize the user environment, reproduction steps, expected behavior, actual behavior, and missing information.

Find the root cause

Use this skill to inspect the relevant code path for this issue. Show the files, line references, call flow, and the likely root cause.

Classify and decide

Use this skill to classify this issue as a bug, architecture limit, feature request, or usage question. Recommend whether to fix it, defer it, or suggest a workaround.

Draft a maintainer response

Use this skill to draft a GitHub reply based on the diagnosis and decision. Explain the current design, user impact, workaround, and next steps.

Best Practices

Read the full issue before drawing conclusions.
Trace the complete code path before naming a root cause.
Get user confirmation before publishing any GitHub reply.

Avoid

Do not classify an issue from the title alone.
Do not blame users for unsupported workflows.
Do not promise fixes without checking scope and test conditions.

Frequently Asked Questions

Does this skill post GitHub comments automatically?

No. It requires user confirmation before any reply is posted.

Can it analyze private repository issues?

Only when the assistant has authorized access to the repository and issue content.

What issue types does it support?

It supports bug reports, feature requests, architecture limits, and usage questions.

Does it write code fixes?

It focuses on triage and response drafting. Code changes require a separate implementation step.

Can non-technical maintainers use it?

Yes. It converts code investigation into concise findings and plain-language replies.

Which assistants can use this skill?

The report lists support for Claude, Codex, and Claude Code.

Developer Details

Author

yunshu0909

License

MIT

Skillstore revision

Version notice

The author did not declare a version.

Repository

https://github.com/yunshu0909/yunshu_skillshub/tree/master/issue-triage

Ref

64ca8af0f54a325752f08bd54e52151061ea659a

Maintenance freshness

7/21/2026

Usage

6 downloads · 159 views

File structure

📄 SKILL.md