By quynhlx
Complete bug fix workflow: Sentry or ClickUp issue investigation, code fix, ClickUp task tracking, and PR creation
Investigate a ClickUp bug task, fix it in code, and open a PR
Triage an external issue report (email, Slack, etc.), check ClickUp sprint, create task if needed, fix the bug, and open a PR
Investigate a Sentry issue, fix the bug, create ClickUp task, and open a PR
Use when a ClickUp bug task needs to be investigated in the codebase, fixed, and delivered as a pull request - the complete lifecycle from ClickUp task to merged code
Use when receiving a bug report or feature request from external sources (email, Slack, verbal) that needs to be triaged against a ClickUp sprint, optionally tracked as a new task, investigated in the codebase, fixed, and delivered as a pull request
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
A Claude Code plugin that automates the complete bug fix lifecycle:
Sentry Issue → Root Cause Analysis → Dev Confirmation → ClickUp Task → Branch → Code Fix → Commit → Dev Review → PR → Status Update
When you encounter a Sentry error, this plugin guides Claude through:
Configure these MCP servers in ~/.claude/settings.json:
{
"mcpServers": {
"sentry": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@sentry/mcp-server"],
"env": {
"SENTRY_AUTH_TOKEN": "<your-sentry-token>"
}
},
"clickup": {
"type": "stdio",
"command": "npx",
"args": ["-y", "clickup-mcp-server"],
"env": {
"CLICKUP_API_TOKEN": "<your-clickup-token>"
}
}
}
}
gh): brew install gh && gh auth login# Clone the plugin
git clone <repo-url> ~/Sources/sbox-bugfix-pipeline
# Register as a local marketplace in Claude Code settings
# Add to ~/.claude/settings.json:
{
"pluginMarketplaces": [
"file:///Users/<you>/Sources/sbox-bugfix-pipeline"
]
}
Then in Claude Code, run: /install-plugin bugfix-pipeline
Copy the skills/ and commands/ directories into your existing plugin cache or ~/.claude/skills/.
/fix-sentry 6704185624
Check Sentry issue 6704185624, fix it, create a ClickUp task, and make a PR.
The skill bugfix-pipeline:sentry-to-pr is automatically available and will be suggested when you mention Sentry issues.
| Convention | Format |
|---|---|
| Branch naming | bugfix/<CustomID>-<short-kebab-description> |
| Commit prefix | [b] [<CustomID>] <description> |
| PR title | [b] [<CustomID>] <ClickUp Task Title> |
| ClickUp task name | [Feature] [Screen] Bug description |
Add to your project's CLAUDE.md:
## Git Remotes
- `origin`: your fork
- `upstream`: main repository (PR target)
The plugin asks the developer to choose the workspace, space, and sprint/folder before creating a task — no assumptions are made.
sbox-bugfix-pipeline/
├── .claude-plugin/
│ └── marketplace.json # Plugin metadata
├── skills/
│ └── sentry-to-pr/
│ └── SKILL.md # Main workflow skill
├── commands/
│ └── fix-sentry.md # /fix-sentry slash command
└── README.md
| Skill | Description |
|---|---|
fix-from-clickup | Read bug details directly from a ClickUp task, understand the issue context, and fix the bug — skipping Sentry investigation |
fix-from-email | Parse bug reports from email, create a ClickUp task for tracking, then investigate and fix the bug |
No model invocation
Executes directly as bash, bypassing the AI model
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub quynhlx/sbox-bugfix-pipeline --plugin sbox-bugfix-pipelineFind and fix a bug. Default is the careful path (reproduce, investigate, test). Add `--fast` for emergency hotfix mode.
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
Sentry-specific agent skills for code review, commits, and more
Debug issues systematically with root cause analysis and execution tracing
Analyzes and fixes GitHub issues using a structured approach with GitHub CLI for issue details, implementing necessary code changes, running tests, and creating proper commit messages.