AgentSkillsCN

shiro_analyze_report

从Shiro报告的产物中创建TiDB漏洞问题,并附上简要的根源分析。当您拥有Shiro报告目录(summary.json/case.sql/plan_replayer.zip),且需要一份可直接提交的GitHub问题正文时,可使用此功能。

SKILL.md
--- frontmatter
name: shiro_analyze_report
description: "Create a TiDB bug issue from Shiro report artifacts and add a short root-cause analysis. Use when a Shiro report directory (summary.json/case.sql/plan_replayer.zip) is available and you need a ready-to-file GitHub issue body."

shiro_analyze_report

Goal

Produce a TiDB bug issue body from a Shiro report, then add a concise Analysis section with 1–3 likely causes.

Required inputs

  • Shiro report directory (e.g., reports/case_0001_...)
  • summary.json

Optional inputs

  • case.sql, schema.sql, data.tsv, inserts.sql
  • plan_replayer.zip

Output

  • A filled issue body using bug-report.md
  • An appended Analysis section

Workflow (deterministic)

  1. Read summary.json and list:
    • SQL (expected/actual)
    • Expected vs actual checksums/counts
    • Oracle and rewrite kind
    • TiDB version
  2. Read case.sql and schema.sql (if present) for minimal repro steps.
  3. Fill bug-report.md fields with concrete values.
  4. Append Analysis:
    • 1–3 likely causes
    • Evidence from SQL or plan signature differences
  5. If asked, run gh issue create; otherwise return the issue body text.

Constraints

  • Issue body must be in English.
  • Keep Analysis short and evidence-backed.
  • If plan_replayer.zip exists, mention it in repro steps.
  • For wrong-result bugs, add labels: sig/planner, severity/major, AI-Testing, fuzz/shiro, and the affected release labels (affects-7.5, affects-8.1, affects-8.5).