AgentSkillsCN

sentry-issues-to-beads

通过 sentry-cli 对 Sentry 问题进行分类，并推荐相应行动方案。适用于当您希望扫描未解决的问题（涵盖所有项目，或指定某项目/问题 ID），判断哪些问题具备可操作性，识别已存在对应 Beads 的重复问题，并在请用户继续推进之前，总结出下一步的处理要点。

SKILL.md
--- frontmatter
name: sentry-issues-to-beads
description: Triage Sentry issues via sentry-cli and recommend actions. Use when you want to scan unresolved issues (all projects or a specified project/issue id), decide which are actionable, detect duplicates that already have beads, and summarize what to do before asking the user to proceed.

Sentry Issues To Beads

Workflow

  1. •

    Confirm prerequisites

    • •Ensure sentry-cli is installed and authenticated (sentry-cli info).
    • •Run sentry-cli --help and confirm the issues subcommand is available.
    • •If org/project defaults are unclear, ask for the org slug and project slug(s).
  2. •

    Determine scope

    • •If the user provides an issue ID, target only that issue.
    • •Else if the user provides project slug(s), scope to those projects.
    • •Else, use all unresolved issues across all projects in the org.
  3. •

    Fetch issues via sentry-cli issues list

    • •Always include is:unresolved in the query.
    • •Typical patterns:
      • •List issues (per project): sentry-cli issues list -o <org> -p <project> --query "is:unresolved"
      • •List issues (all projects in org): sentry-cli issues list -o <org> --query "is:unresolved"
      • •Single issue: sentry-cli issues list -o <org> -p <project> --id <issue_id>
    • •If pagination is required, use --pages and/or --max-rows to match the user-specified limit.
    • •If listing without --project fails, iterate per project instead.
  4. •

    Check for duplicates

    • •Look for existing beads that already track the issue (search by issue ID, short ID, or Sentry URL).
    • •If a duplicate is found, ignore the issue and record it under a "duplicates" list with the matching bead ID.
  5. •

    Triage for actionability

    • •Use judgment only (no hard cutoff).
    • •If an issue looks non-actionable (e.g., stale, insufficient context, flake/noise), mark it as non-actionable.
    • •For every non-actionable issue, record a short reason.
  6. •

    Recommend actions (do not execute yet)

    • •For actionable issues, recommend creating one bead per issue (no epic).
    • •Suggested bead fields:
      • •Title: Sentry: <issue title>
      • •Description: issue summary, shortId/id, culprit, last seen, level, environment/tags, link
      • •Design: hypotheses about root cause + next debugging steps
      • •Acceptance: issue resolved + validation plan (e.g., fix confirmed, no new events after deploy)
  7. •

    Report results and ask to proceed

    • •Provide three lists:
      • •Actionable (recommend bead) with issue links
      • •Non-actionable (recommend close/ignore) with reasons
      • •Duplicates (already tracked) with bead IDs
    • •Summarize counts for each category.
    • •Ask the user whether to proceed with actions, such as:
      • •create beads for actionable issues
      • •close or ignore non-actionable issues
    • •If the user confirms, perform the requested actions.