bugbot

Automate Cursor Bugbot review fixes on GitHub pull requests.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/EdgeApp/edge-dev-agents --skill bugbot-edgeapp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugbot
Source: https://github.com/EdgeApp/edge-dev-agents/tree/main/.cursor/skills/bugbot
Command: npx skills add https://github.com/EdgeApp/edge-dev-agents --skill bugbot-edgeapp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, jq, node, and includes scripts (resource) components.

What problem does it solve?

This skill automates the tedious process of addressing Cursor Bugbot review findings, ensuring PRs reach a clean state without manual intervention or repetitive cycles.

Core Features & Use Cases

  • Automated Scan Cycles: Executes scan cycles to classify unresolved bot threads and apply necessary fixup commits.
  • Intelligent Scheduling: Self-manages recurring 5-minute cycles on Claude Code to monitor PR status until the bot reports a clean state.
  • Conflict Management: Automatically slots fixup commits next to their targets and handles rebase conflicts gracefully.

Quick Start

Invoke the bugbot skill by providing the repository and pull request number to begin the automated cleanup process.

Frequently Asked Questions about bugbot

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

FAQPage Schema
How do I automate pull request review cleanup for bot findings on GitHub?

You can automate pull request review cleanup by invoking a skill that scans PR threads, classifies unresolved bot comments, applies fixup commits, and schedules recurring 5-minute verification cycles until the PR reaches a clean state.

Does automated PR review fixup require specific tools like the GitHub CLI and node?

Automated PR review fixup requires git, the GitHub CLI, jq, and node.js installed. These dependencies execute companion scripts, manage PR state transitions, and process bot thread data to apply fixup commits correctly.

How does automated code review handle rebase conflicts when applying fixup commits?

Automated code review handles rebase conflicts gracefully by slotting fixup commits directly next to their target commits during scan cycles. This targeted placement minimizes merge conflicts while managing bot-identified issues.

What's the best way to resolve Cursor Bugbot review findings without manual intervention?

The best way to resolve Cursor Bugbot findings without manual intervention is using an automated skill that self-manages recurring 5-minute cycles on Claude Code to monitor PR status, applying fixup commits until the bot reports a clean state.

Can I monitor GitHub pull request check-run status automatically after applying code fixes?

You can monitor GitHub pull request check-run status automatically through self-managing recurring 5-minute cycles that verify check-run status after applying fixup commits, ensuring the PR reaches a clean state without continuous manual checks.

When should I avoid automating bot review thread resolution on pull requests?

You should avoid automating bot review thread resolution when dealing with complex architectural changes requiring human judgment, or when the repository lacks the necessary git, GitHub CLI, jq, and node.js environment to execute companion scripts and manage PR state transitions.