From sbox-bugfix-pipeline
Use when a Sentry error issue needs to be investigated, fixed in code, tracked as a ClickUp bug task, and delivered as a pull request - the complete bug fix lifecycle from error report to merged code
How this skill is triggered — by the user, by Claude, or both
Slash command
/sbox-bugfix-pipeline:sentry-to-prThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Complete bug fix lifecycle: Sentry error investigation → root cause analysis → ClickUp task creation → branch → code fix → commit → developer review → PR → task status update. Automates the full loop from production error to deliverable fix.
Complete bug fix lifecycle: Sentry error investigation → root cause analysis → ClickUp task creation → branch → code fix → commit → developer review → PR → task status update. Automates the full loop from production error to deliverable fix.
Required MCP servers:
Required CLI tools:
gh (GitHub CLI) — authenticated for PR creationgit — with remotes configureddigraph sentry_to_pr {
rankdir=TB;
node [shape=box, style=rounded];
investigate [label="1. Investigate\nSentry Issue"];
rootcause [label="2. Find Root Cause\nin Codebase"];
confirm1 [label="Confirm Root Cause\nwith Dev", shape=diamond];
clickup [label="3. Create ClickUp\nBug Task"];
branch [label="4. Create Branch"];
fix [label="5. Fix the Bug"];
commit [label="6. Commit"];
review [label="Dev Manual Review", shape=diamond];
pr [label="7. Create PR"];
update [label="8. Update ClickUp\nStatus"];
done [label="Done", shape=doublecircle];
investigate -> rootcause;
rootcause -> confirm1;
confirm1 -> clickup [label="approved"];
clickup -> branch;
branch -> fix;
fix -> commit;
commit -> review;
review -> pr [label="approved"];
pr -> update;
update -> done;
}
Input: Sentry issue ID (numeric) or issue slug (e.g. PROJECT-ABC)
mcp__sentry__find_organizations → get organizationSlug and regionUrlmcp__sentry__get_issue_details with issueId, organizationSlug, regionUrlInvoke the superpowers:systematic-debugging skill to guide the investigation:
Grep across the relevant module⏸ STOP — Confirm with developer before proceeding.
Present the root cause analysis to the developer and ask for confirmation using AskUserQuestion:
Ask the developer which workspace, space, and sprint/folder to use — do NOT assume the latest sprint.
Use AskUserQuestion to confirm:
mcp__clickup__get_workspaces and let the developer choosemcp__clickup__get_spaces and let the developer chooseCreate the task:
mcp__clickup__create_task with:
[Feature] [Screen] <Bug description> (e.g. [Aged Care GP] [Referral Form] Fix null reference on submit)2 (high)["bug", "sentry"]Save the ClickUp Custom ID (the custom task ID, e.g. PROJ-123) and task title — these are used for branch naming and PR title.
git checkout master && git pull
git checkout -b bugfix/<CustomID>-<short-kebab-description>
Invoke the superpowers:test-driven-development skill to guide the fix:
Commit message format:
[b] [<CustomID>] <Short description of the fix>
<Root cause explanation in 1-2 sentences>
Fixes <SENTRY-ISSUE-ID>
Stage changed files and commit.
⏸ STOP — Present the fix for developer review before creating PR.
Use AskUserQuestion to present:
If the developer requests changes, go back to step 5 and amend. Only proceed when approved.
PR title format: [b] [<CustomID>] <ClickUp Task Title>
PR body format:
## Summary
- <What was fixed and why>
- <What was changed>
## Root Cause
<Detailed explanation of why the error occurred>
## Files Changed
- <list of files>
## Test plan
- [ ] <Steps to verify the fix>
**Sentry Issue:** <sentry-url>
**ClickUp Task:** <clickup-url>
Steps:
-u flaggh pr create targeting masterupstream remote and use GH_REPO env varAfter the PR is created successfully:
mcp__clickup__update_taskmcp__clickup__create_task_comment| Mistake | Fix |
|---|---|
| Fixing symptoms, not root cause | Always trace the full call chain before coding |
| Searching minified/compiled output instead of source | Identify the module from error context, then search source files (.ts, .js, .py, etc.) |
| Wrong ClickUp sprint/folder | Always ask the developer — never assume |
| Skipping dev confirmation | Always pause after root cause analysis — the developer must agree before fixing |
| Creating PR without dev review | Always present the fix and get approval before creating the PR |
| PR fails due to fork permissions | Push branch to the upstream remote directly, or use --head owner:branch |
| Overly broad fix | Fix only what the Sentry error reports — no refactoring |
[Feature] [Screen] Bug description formatbugfix/<CustomID>-<desc>[b] [CustomID] ClickUp Title formatnpx claudepluginhub quynhlx/sbox-bugfix-pipeline --plugin sbox-bugfix-pipelineAutomatically triages errors from Sentry or logs, cross-references git history/open PRs/codebase, prioritizes by severity, and opens fix PRs.
Analyzes and resolves Sentry issues posted as GitHub PR review comments. Fetches comments, parses bug details, and applies fixes.
Fixes GitHub issues using parallel analysis, hypothesis-based root cause analysis, similar issue detection, and prevention recommendations. Use for debugging errors, regressions, bugs, or triaging.