code-review-bugsnag

Analyze GitHub pull requests against Bugsnag error stack traces and acceptance criteria.

Updated Jan 6, 2023

Search Tags:#automation #code review #debugging #pull request #github #bugsnag

Ready to run

npx skills add https://github.com/pekral/phpstan-rules --skill code-review-bugsnag

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-bugsnag
Source: https://github.com/pekral/phpstan-rules/tree/main/.claude/skills/code-review-bugsnag
Command: npx skills add https://github.com/pekral/phpstan-rules --skill code-review-bugsnag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, jq, and includes scripts (resource) components.

What problem does it solve?

This skill bridges the gap between production errors and code fixes by automating the technical review of pull requests linked to Bugsnag issues, ensuring that fixes are verified, tested, and documented without manual overhead.

Core Features & Use Cases

Contextual Analysis: Automatically gathers Bugsnag error details, stack traces, and linked GitHub PRs to provide a comprehensive review environment.
Automated Gatekeeping: Enforces strict code review standards, including functional compliance, security checks, and refactoring analysis, directly on the linked PR.
Consolidated Reporting: Publishes technical findings to GitHub and non-technical summaries to Bugsnag, keeping both developers and stakeholders informed.

Quick Start

Use the code-review-bugsnag skill to review the fix for the Bugsnag error at the provided dashboard URL.

Frequently Asked Questions about code-review-bugsnag

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

FAQPage Schema

How do I automate code reviews for pull requests linked to Bugsnag errors?▼

Automated Bugsnag error code reviews gather stack traces and linked GitHub pull requests to analyze code changes against acceptance criteria. This identifies critical bugs, security vulnerabilities, and technical debt, publishing structured technical findings to GitHub.

What is the best way to verify a production error fix against its acceptance criteria?▼

Verifying a production error fix involves bridging Bugsnag error details with GitHub pull request changes. Automated gatekeeping enforces strict code review standards, ensuring the fix is functional, secure, and properly documented without manual overhead.

Do I need curl and jq to review pull requests associated with Bugsnag issues?▼

Yes, you need curl and jq to integrate with GitHub and Bugsnag APIs. These dependencies allow the automated review process to fetch error details, stack traces, and publish consolidated reports back to the platforms.

Can I publish non-technical summaries of Bugsnag code fixes for stakeholders?▼

Publishing non-technical summaries for stakeholders is supported by sending consolidated reports directly to Bugsnag. This keeps cross-functional teams informed about the verification status while technical findings go to GitHub.

How does automated code review handle security vulnerabilities and technical debt?▼

Automated code review handles security vulnerabilities and technical debt by analyzing code changes against error stack traces. It enforces strict gatekeeping standards to verify functional compliance, security checks, and refactoring analysis on linked pull requests.

When should I not use automated gatekeeping for Bugsnag error pull requests?▼

Automated gatekeeping for Bugsnag error pull requests is not suitable when manual intervention is required for complex logic. It is designed for verifying documented fixes, security checks, and refactoring analysis, not exploratory debugging.