Triage Airbrake error groups, analyze backtraces, and create pull requests.
npx skills add https://github.com/przbadu/skills-factory --skill airbrake-fixer
Please help me install this Agent Skill. Skill: airbrake-fixer Source: https://github.com/przbadu/skills-factory/tree/main/skills/airbrake-fixer Command: npx skills add https://github.com/przbadu/skills-factory --skill airbrake-fixer
This Skill removes the manual toil of investigating production Airbrake errors, tracing them back to the right code path, and turning a noisy error queue into a targeted fix.
Use the airbrake-fixer skill to inspect the Airbrake project, rank unresolved production errors, and fix the selected issue in a worktree.
High-intent search queries and answers about installing and using this skill.
To fix production Airbrake errors automatically, you need a workflow that scans unresolved incidents, ranks them by occurrence count, and isolates the code fix in a git worktree before creating a pull request. This removes the manual toil of investigating Airbrake backtraces and tracing them back to the right code path.
Triage unresolved Airbrake error groups by ranking them according to occurrence count to identify the highest-impact issue. This process drills into occurrence details to capture backtraces, parameters, and session data for root-cause analysis.
Yes, you can isolate Airbrake bug fixes using a git worktree to apply the minimal code change. This dedicated isolation ensures the production fix is validated and prepared for a pull request with minimal disruption to your main branch.
Airbrake root-cause analysis requires backtrace, parameters, environment, and session data from the occurrence details. Capturing this deep context allows you to trace the exception back to the correct code path and implement a targeted fix.
Yes, Chrome browser automation is required to open Airbrake occurrence details and capture the backtrace, parameters, environment, and session data. This automated extraction feeds the root-cause analysis needed to prepare the fix.
To create a pull request after fixing a production exception, apply the minimal code change in an isolated git worktree, validate the result, and prepare the PR. This workflow turns a noisy error queue into a reviewed fix with minimal disruption.
przbaduDiagnose and rank production performance issues from New Relic, Logtails, PGHero, and Airbrake telemetry.
coco-researchPush a verified branch and create a merge-ready pull request.
sei-newbearAutomate Git branch, worktree, pull request, and merge workflows.
Sahib-Sawhney-WHDiagnose DAPR error codes with root-cause analysis and remediation steps.
