Stats
Links
Categories
qa-debug
qa-debug is a Claude Code plugin that brings structured, pessimistic quality assurance and debugging methodology directly into your development workflow. It gives QA engineers, solo developers, and software teams a consistent, human-in-the-loop framework for triaging bugs, running structured debugging sessions, designing resilience tests, and archiving errors — all driven by Claude, with nothing executing automatically without your approval.
What It Does
The problem it solves
Most AI-assisted debugging is optimistic: the model proposes a fix and runs it. This is fast but dangerous. In production environments, unreviewed code execution causes more incidents than it prevents. qa-debug inverts this: Claude proposes, you approve, nothing runs automatically.
The plugin also solves the fragmentation problem. Triage, root cause analysis, chaos testing, mutation testing, contract testing, post-mortems, and error archiving are currently handled by different tools, processes, and team members with no shared vocabulary. qa-debug unifies them under a single plugin with a common output format and a shared error archive.
Who benefits
- QA engineers who want structured, reproducible test planning and a blameless incident retrospective format
- Backend developers who need a systematic debugging framework that does not skip steps under pressure
- Solo builders who do not have a QA team and need to compensate with rigorous methodology
- Team leads who want a consistent debugging process that every team member follows the same way
Requirements
- Claude Code CLI v2.1.51 or higher
- Node.js 18 or higher (required by MCP servers)
- Active accounts: GitHub, Linear, Sentry (required for MCP server authentication)
- Shell: bash or zsh (PowerShell for Windows users running the install commands)
Installation
Step 1 — Clone or download the plugin folder
# Clone from GitHub
git clone https://github.com/luxcordia/qa-debug.git
# Or download and extract the archive
tar -xzf qa-debug-v1.3.0.tar.gz -C /your/plugins/folder/
Step 2 — Set environment variables
Add these to your shell profile (.bashrc, .zshrc, or PowerShell $PROFILE). Replace the placeholder values with your real tokens — never commit real tokens to version control.
bash / zsh:
# GitHub personal access token (repo + read:org scopes)
export GITHUB_TOKEN=ghp_YourTokenHere
# Linear API key (from Linear → Settings → API)
export LINEAR_API_KEY=lin_api_YourKeyHere
# Sentry auth token (from Sentry → Settings → Auth Tokens)
export SENTRY_AUTH_TOKEN=sntrys_YourTokenHere
# Sentry organization slug (the subdomain of your Sentry URL)
export SENTRY_ORG=your-org-slug
PowerShell (Windows):
$env:GITHUB_TOKEN = "ghp_YourTokenHere"
$env:LINEAR_API_KEY = "lin_api_YourKeyHere"
$env:SENTRY_AUTH_TOKEN = "sntrys_YourTokenHere"
$env:SENTRY_ORG = "your-org-slug"
Reload your shell (source ~/.zshrc or open a new terminal) before proceeding.
Step 3 — Register the marketplace and install the plugin
macOS / Linux:
# Register the local marketplace (one-time setup)
claude plugin marketplace add local-marketplace /path/to/qa-debug-parent-folder
# Install the plugin
claude plugin install qa-debug@local-marketplace
Windows (PowerShell):
# Register the local marketplace (one-time setup)
claude plugin marketplace add local-marketplace "C:\path\to\qa-debug-parent-folder"
# Install the plugin
claude plugin install qa-debug@local-marketplace
Step 4 — Authorize Linear and Sentry via OAuth
/mcp
In the MCP panel, find project-tracker and monitoring, then follow the OAuth flow to authorize Linear and Sentry respectively. GitHub authenticates via the personal access token set in Step 2 — no additional OAuth step is required.
Step 5 — Verify installation
claude mcp list
Expected output:
source-control Connected
project-tracker Connected
monitoring Connected
If any server shows Disconnected, confirm the corresponding environment variable is set and non-empty, then restart Claude Code.
Commands
All commands use the /qa-debug: prefix and are available immediately after installation.