bugbot-review

Generates deduplicated code review findings from BUGBOT.md and whole-diff analysis.

Updated May 18, 2025
One-click install
npx skills add https://github.com/nthpaul/dotfiles --skill bugbot-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugbot-review
Source: https://github.com/nthpaul/dotfiles/tree/main/cursor/.cursor/skills/bugbot-review
Command: npx skills add https://github.com/nthpaul/dotfiles --skill bugbot-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bugbot-guided code reviews can produce noisy or overlapping findings, making it harder to quickly identify the most actionable issues in a pull request or branch diff.

Core Features & Use Cases

  • Bugbot guidance discovery: Finds relevant BUGBOT.md files by matching both path and topic coverage against the changed files, including .cursor/BUGBOT.md when present.
  • Layered review passes: Runs one review pass per relevant BUGBOT.md plus a global whole-diff pass to catch issues not covered by local guidance.
  • Finding deduplication & actionability: Dedupes findings by file and line span plus a normalized title, then outputs only severity-tagged, explainable issues with locations and sources.
  • PR-aware behavior: Detects whether the current branch is associated with a PR and reports that status; for PRs it supports inline GitHub review comment posting with dedupe against existing threads.

Quick Start

Run the bugbot-review skill to review the current PR (or the branch diff when no PR is found) and produce deduped, actionable findings.

Frequently Asked Questions about bugbot-review

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

FAQPage Schema
How do I get deduplicated code review findings on a GitHub pull request?

Static analysis for pull requests reduces noisy code review findings by deduplicating overlapping issues using file, line span, and normalized titles. It combines scoped BUGBOT.md guidance with a global whole-diff analysis to output only high-signal, severity-tagged issues with locations and sources.

How does whole diff analysis work for finding bugs in a branch without a PR?

Whole diff analysis for finding bugs in a branch without a PR computes changes from a base commit to HEAD. It then executes a global review pass to catch issues not covered by local BUGBOT.md guidance, outputting severity-tagged findings with location and source details.

Can I post inline GitHub review comments without creating duplicate threads?

Yes, you can post inline GitHub review comments without creating duplicate threads. The review process detects existing PR threads and dedupes new findings against them using file, line span, and normalized titles before posting inline comments.

How do I apply custom static analysis rules to changed files in a code review?

You apply custom static analysis rules to changed files by defining them in BUGBOT.md files. The review process discovers these files via path and topic matching against the changed files, including .cursor/BUGBOT.md, and runs a dedicated layered review pass for each.

What is the best way to reduce noise from automated code reviews on a pull request?

The best way to reduce noise from automated code reviews on a pull request is to dedupe findings by file, line span, and normalized titles. This approach filters overlapping issues, outputting only severity-tagged, explainable issues with clear locations and source references.