triage-issue

仓库创建 2026年6月21日最近提交 21 天前SkillHot 收录 21 天前
▸ 精选理由

避免重复建票并产出结构化的缺陷描述,适合运维与工程一线响应。

▸ 风险提示

会读取项目历史与问题数据,需 Jira 访问权限。

这个 Skill 做什么

对错误报告或堆栈追踪进行去重与定位,先查找重复项再创建或更新 Jira 票。

把用户贴过来的报错、堆栈或缺陷描述拿去在 Jira 里查重,先找有没有已有票或已修复的相关问题,再决定创建或更新工单。适合有人问“这是不是已知问题/重复票/有没有被修好”或要求“帮我提个 bug”时使用。流程的重点是先去重再建票,避免重复劳动。

▸ 展开 SKILL.md 英文原文

Triage a bug report or error message against Jira with the atl CLI — search for duplicates and prior fixes first, then create a well-structured ticket or comment on an existing one. USE WHEN the user pastes an error, stack trace, or bug description and asks "is this known", "is this a duplicate", "has this been reported/fixed before", or "file a bug for this".

开发编程问题分流重复查找Jira通用
0
Stars
0
Forks
30
仓库内 Skill
+0
7 日增星
安装 / 使用
给你的 Agent 一句话(通用)
帮我安装这个 skill:https://raw.githubusercontent.com/isukharev/atl/main/plugins/atl/skills/triage-issue/SKILL.md
或 curl 直取 SKILL.md
curl -fsSL "https://raw.githubusercontent.com/isukharev/atl/main/plugins/atl/skills/triage-issue/SKILL.md"
SKILL.MD 节选查看完整文件 ↗
<!-- Generated from skills-src/triage-issue/SKILL.md — edit the source and run 'make gen-plugins'. -->

# Triage an issue with `atl`

Find duplicates **before** filing. Never create a ticket without first showing
the user what already exists. Command details live in the `jira` skill.

**Preflight:** `atl` must be installed and configured. If `command -v atl` fails
or a command exits `7` ("not configured"), run `$setup` and stop.

## Workflow

### 1. Extract the error signature

From the report, pull: the exception/error type, the failing
class/function/endpoint, and the stable message words. Strip volatile parts —
ids, timestamps, hostnames, line numbers — they poison text search. Build 2–3
via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有