withastro/astro

triage

Triage a bug report.

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/withastro/astro --skill triage

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

Triage

Triage a bug report end-to-end: reproduce the bug, diagnose the root cause, verify whether the behavior is intentional, and attempt a fix.

General Rules

Do not get stuck on infrastructure problems. If a server won't start, a port is blocked, or a tool is unavailable in the CI environment — bail out after 2 attempts and write your report with the data you already have. Looping on server restarts or missing CLI tools wastes your entire time budget. A partial report with solid findings is infinitely more valuable than no report because you ran out of time fighting a stale process.

Input

You need either:

  • issueTitle and issueBody provided in args (preferred — use these directly as the bug report), OR
  • A GitHub issue number or URL mentioned in the conversation (use gh issue view to fetch details)

If a triageDir is provided in args, use that as the working directory for the triage. Otherwise, default to triage/gh-<issue_number> (if you have an issue number) or triage/current.

Step 1: Reproduce

Read and follow reproduce.md. Use a subagent for this step to isolate context.

After completing reproduction, check the result:

  • If the issue was skipped (host-specific, unsupported version, etc.) — skip to Output.
  • If the issue was not reproducible — skip to Output.
  • If the issue was reproduced — continue to Step 2.

Step 2: Diagnose

Read and follow diagnose.md. Use a subagent for this step to isolate context.

After completing diagnosis, check your confidence:

  • If confidence is low — skip to Output.
  • If confidence is medium or high — continue to Step 3.

Step 3: Verify

Read and follow verify.md. Use a subagent for this step to isolate context.

After completing verification, check the verdict:

  • If the verdict is intended-behavior — skip to Output. The issue is not a bug; do not attempt a fix.
  • If the verdict is bug or unclear — continue to Step 4.

Step 4: Fix

Read and follow fix.md. Use a subagent for this step to isolate context.

Whether the fix succeeds or fails, continue to Output.

Output

After completing the triage (or exiting early), return your structured results so the orchestrator can post a comment and manage labels.

来自同一仓库

更多 Skills

全部 Skills
withastro
社区

analyze-github-action-logs

Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements. Use when asked to "analyze workflow logs", "review action runs", or "analyze GitHub Actions".

1小时安装量
4
GitHub Stars
6.3万
最近更新
10月23日
withastro
社区

astro-adversary-blue

Independently implement and validate an alternative solution for an Astro pull request. Use only for Factory's adversary blue team.

1小时安装量
4
GitHub Stars
6.3万
最近更新
10月23日
withastro
社区

astro-adversary-purple

Qualify and compare red and blue solutions for an Astro pull request using Astro-specific merge and tie-break criteria. Use only for Factory's adversary purple team.

1小时安装量
4
GitHub Stars
6.3万
最近更新
10月23日
withastro
社区

astro-code-review

Perform a static, read-only code review of an Astro pull request or of a local branch, commit range, diff, patch, or working tree being prepared as a pull request. Determine whether the change satisfies its stated business requirements and is good enough to merge, using the PR description, linked requirement issues and roadmap items, and PR or issue discussions when available. Use this skill only for PR review or self-review, not issue triage or bug investigation. It reports only merge-relevant

1小时安装量
4
GitHub Stars
6.3万
最近更新
10月23日