跳到正文
cccskills
免费在 GitHub 公开

triage

Review open GitHub issues for herdr and organize them into a concise Markdown table. Each row shows urgency, a recommended action, issue age, reactions, and a short reason to help decide what needs attention.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Triage open herdr GitHub issues into a concise decision-first Markdown table. Use when the user says "triage", asks to triage open issues, asks which issues need attention, or wants issue priority/recommendation lights for herdr.

集成工具GitHub
查看安装方法

适用场景

  • Deciding which open issues need immediate fixes
  • Preparing a queue of feature requests and quality improvements
  • Reviewing older issues and reports that need more evidence

包含的文件(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Herdr Issue Triage

Use this skill only inside the herdr repository.

When the user says triage, inspect open GitHub issues for herdrdev/herdr and return a concise Markdown table. Prefer GitHub MCP tools when available. If they are unavailable, use gh issue list / gh issue view only when authenticated access is already configured.

Use this table shape:

LightRecommendationIssueAgeReactionsWhy
🔴fix now#12318d5user-visible regression
🟡queue#12442d2useful but not blocking
🔵defer#1257d0cosmetic polish

Keep issue numbers as Markdown links. Use days since issue creation for Age. Use total reactions for Reactions; include a compact breakdown only when it changes interpretation, such as 7 (5 👍, 2 👀).

Classify with these lights:

  • 🔴 fix now: reproducible bug, crash, data loss, blocked workflow, release risk, or high-confidence user-visible regression.
  • 🟡 queue: useful feature, important quality issue, repeated user signal, stale issue that still looks valid, or behavior worth scheduling.
  • 🔵 defer: cosmetic polish, low-signal idea, unclear report, docs-only nit, or issue that likely needs more evidence before implementation.

Recommendations should be short imperative phrases: fix now, queue, defer, needs repro, close?, or needs owner decision.

Write one sentence before the table only if needed to state scope, such as how many open issues were inspected. After the table, add at most one short note for uncertainty or follow-up. Do not produce a long narrative unless the user asks for depth.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

herdr

免费

Control terminals and coding agents inside Herdr, a tool that groups multiple terminals. Create split panes, run commands, send agent prompts, read output, and wait for status changes while coordinating work across the current session.

中文简介正在准备中。当前显示英语简介。

  • Starting another coding agent in a neighboring pane
  • Running tests or a server in a separate terminal pane
  • Reading agent output and checking whether input is needed
herdrdev/herdr4.5万2026年10月16日 更新

Check release readiness inside the herdr repository by comparing changes since the base release with upcoming release notes and documentation. Review CLI descriptions, issue references, checks, and benchmarks, then report readiness.

中文简介正在准备中。当前显示英语简介。

  • Check release notes against changes since the base release
  • Review upcoming documentation before a release
  • Inspect issue references that release CI will close
herdrdev/herdr4.5万2026年10月16日 更新

Create a disposable Herdr session to reproduce terminal, process, API, or agent issues separately from the main session. Drive tests through the CLI or API, collect evidence of state changes, and clean up the temporary session afterward.

中文简介正在准备中。当前显示英语简介。

  • Reproducing pane, terminal, or process issues in Herdr
  • Checking agent detection and permission-related state changes
  • Collecting commands, logs, and state for a reproducible bug report
herdrdev/herdr4.5万2026年10月16日 更新

查看 herdrdev 的全部技能

报告此技能的问题