sentry-backend-bugs

Detect high-priority bug patterns in Sentry backend Python/Django diffs.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/Harigithub11/sentry --skill sentry-backend-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sentry-backend-bugs
Source: https://github.com/Harigithub11/sentry/tree/main/.agents/skills/sentry-backend-bugs
Command: npx skills add https://github.com/Harigithub11/sentry --skill sentry-backend-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps backend engineers identify and diagnose production-caused bugs in Python/Django projects by matching patterns from real-world incidents, diffs, and code changes.

Core Features & Use Cases

  • Pattern-based bug detection across backend changes by scanning diffs and checking against known production issues.
  • Guided triage using Read and Grep to trace data flow from diffs to ORM and serialization boundaries.
  • Prioritized reporting of HIGH and MEDIUM confidence findings to assist code reviews and PR audits.
  • Use during backend diffs, PR reviews, Warden findings, and production-error pattern audits in src/ and tests/.

Quick Start

Provide the backend diff or current branch changes for analysis.

Frequently Asked Questions about sentry-backend-bugs

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

FAQPage Schema
How do I find production-caused bugs in a Django diff?

To find production-caused bugs in a Django diff, apply pattern-based detection to scan changed hunks and trace data flow outward to ORM boundaries. This identifies high-priority backend issues rooted in real-world incidents during code review.

How does diff analysis trace Django ORM data flow for bug patterns?

Diff analysis traces Django ORM data flow by using Read and Grep tools to expand outward from changed code hunks. It follows ORM and serialization boundaries to classify and report high or medium confidence bug patterns.

Can I use this to audit Python backend code for production error patterns?

Yes, you can audit Python backend code for production error patterns by scanning diffs and current branch changes. It matches modifications against known production issues to assist PR audits and Warden findings in src and tests directories.

What is the best way to triage backend bug findings during a PR review?

The best way to triage backend bug findings is to prioritize HIGH and MEDIUM confidence reports generated from the diff analysis. This focuses your PR review on real production issues matched within the Python/Django codebase.

Do I need a specific branch or diff to start detecting backend bugs?

You need to provide a backend diff or current branch changes to start detecting backend bugs. The analysis begins directly from the changed hunk and expands outward as needed to trace data flow and classify findings.