bugteam

Automates multi-loop pull request audit and fix cycles until convergence on GitHub.

6|1|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/jl-cmd/claude-dev-env --skill bugteam-jl-cmd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugteam
Source: https://github.com/jl-cmd/claude-dev-env/tree/main/packages/claude-dev-env/.agents/skills-archived/bugteam
Command: npx skills add https://github.com/jl-cmd/claude-dev-env --skill bugteam-jl-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Reviewing a pull request thoroughly requires repeated audit-and-fix rounds, and driving each round manually is slow and error-prone. This Skill automates the full cycle: it gates the diff against CODE_RULES, spawns a clean-room audit agent each loop, dispatches a fix agent for the findings, posts per-loop GitHub reviews, and stops only when the PR converges, hits the 20-loop cap, or gets stuck. ## Core Features & Use Cases - Clean-room audit loops: Each loop spawns a fresh code-quality-agent (opus) with no inherited context, auditing all 17 categories (A–Q) from API contracts to concurrency hazards, with findings posted as one anchored GitHub PR review per loop. - Targeted automated fixes: A fresh clean-coder worker receives only the latest audit's findings, applies narrow fixes, runs tests, commits and pushes, then replies to and resolves each review thread. - Deterministic quality gate: A code_rules_gate.py pre-audit check must pass before every audit, with up to 5 standards-fix rounds to clear violations. - Use Case: Before requesting human review on a large PR, run /bugteam to autonomously iterate audit and fix loops until the diff reports 0 P0/P1/P2 findings, with a full loop log and final report on exit. ## Quick Start Run /bugteam on the current branch's open pull request to start the automated audit-fix loop until it converges.

Frequently Asked Questions about bugteam

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix a pull request until it passes code review?▼

Invoke /bugteam on a branch with an open PR. It runs a CODE_RULES gate, spawns a fresh audit agent each loop, dispatches a fix agent for the findings, and repeats until the audit reports zero findings or the 20-loop cap is reached.

What does the bugteam audit check in a pull request?▼

The audit walks 17 categories (A–Q) covering API contracts, resource cleanup, silent failures, security boundaries, concurrency hazards, CODE_RULES compliance, test-name verification, and cross-surface claim consistency. Each category must produce a finding or verified-clean evidence with a traced code path.

Can I run bugteam without the gh CLI or GitHub access?▼

No. The skill requires the gh CLI, authenticated status, and push permission on the repository, verified by a transport check before any GitHub step. If checks fail, it routes through the pr-loop-cloud-transport skill's substitution matrix first.

Why does bugteam refuse to run on my branch?▼

It refuses when there is no PR or upstream diff, when the working tree has uncommitted changes, when required subagents are missing on tier 2, or when CLAUDE_REVIEWS_DISABLED contains the token bugteam. Each refusal prints an exact quoted line and stops.

What happens when bugteam hits the 20-loop limit?▼

The loop exits with reason 'cap reached' and prints the remaining P0/P1/P2 finding counts, recommending /pr-converge for human triage. The cap counts audit completions only; standards-fix passes before an audit do not advance the counter.

How does bugteam keep audits independent between loops?▼

Every loop spawns a fresh worker process or fresh agent context whose prompt contains only the PR scope, audit rubric, and loop number. Prior loop history stays in the lead session, so each audit starts from first principles without inherited verdicts.