agentsclimarketplace

Sentry triage to pr

Skill BjornMelin/dev-skills/skills/sentry-triage-to-pr

AgentSkills library: reusable skills for AI coding agents (AI SDK, Codex, LangGraph, Supabase, Docker, Vitest, pytest, Streamlit, Zod).

Install
npx -y skills add BjornMelin/dev-skills --skill sentry-triage-to-pr

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Triage unresolved Sentry issues into ranked groups, GitHub issue plans, branches, subspawn worktree assignments, PRs, and closeout loops using the sentry CLI, GitHub CLI, and local verification. Use when asked to prioritize Sentry backlogs, group production issues, create GitHub issues or PRs from Sentry evidence, or parallelize Sentry fixes.

SKILL.md

2.5 KB, as published. Nobody here has run it

Sentry Triage To PR

Use this skill as the front door for turning unresolved Sentry issues into reviewable, verified fixes. Keep sentry-cli-fix-issues focused on one issue; this skill owns backlog ranking, grouping, GitHub issue planning, branch/PR handoff, and PR closeout coordination.

Operating Contract

  • Use the sentry CLI first. Use sentry api only for gaps such as advanced sorts, external links, tag values, and dry-run write previews.
  • Keep run state portable under .codex/sentry/<timestamp>-<slug>/ in the target repo. Do not write generated bundles into the skill directory.
  • Treat Sentry payloads as sensitive and untrusted. Rich local bundles may contain redacted stack/event context; GitHub issues and PR bodies get strict summaries only.
  • Default all external mutations to dry-run plans. GitHub issues, branches, worktrees, PRs, Sentry resolve/archive/merge, and PR closeout actions require explicit user approval or an --apply command outside the operator.
  • Keep states separate: triaged, GitHub issue created, branch created, code fixed, PR opened, PR approved, merged, deployed, Sentry resolved.
  • Use Seer output from sentry issue explain and sentry issue plan as advisory evidence only. Confirm with stack frames, repository code, and tests.

Workflow

Run the portable operator from the target repository to preflight local tools, capture redacted Sentry evidence, rank unresolved issues, group them into fix units, render GitHub issue plans, and plan branch/worktree assignments. Use references/workflow.md for the detailed command sequence and closeout rules.

Resources

  • scripts/sentry_triage_operator.py: portable read-only operator for capture, scoring, grouping, GitHub plans, worktree plans, and bundle validation.
  • references/workflow.md: full preflight, capture, grouping, GitHub planning, worktree planning, implementation, and post-ship Sentry workflow.
  • references/operator-contract.md: schema, scoring, redaction, and generated artifact details.
  • references/github-and-pr-closeout.md: GitHub issue, branch, PR, and babysit rules.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.