Jeri - Bug Reporter

Collect structured bug report details and create classified Linear issues.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/JeriCommerce/claude-plugins --skill jeri-bug-reporter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Jeri - Bug Reporter
Source: https://github.com/JeriCommerce/claude-plugins/tree/main/plugins/bug-reporter/skills/bug-reporter
Command: npx skills add https://github.com/JeriCommerce/claude-plugins --skill jeri-bug-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces ambiguous and incomplete bug reports by guiding reporters through a conversational, structured process and turning their responses into well-classified issues in Linear so engineering can triage and act quickly.

Core Features & Use Cases

  • Guides users through step-by-step questions to capture what happened, where it happened, who reported it, reproduction steps, and optional attachments.
  • Classifies priority and area labels, checks for duplicates, and creates a formatted issue in the project's Support and Customer Bugs project using the Linear connector.
  • Handles attachments (screenshots/videos) and enforces English for issue content so development receives consistent, actionable reports.
  • Use Case: A support agent reports a merchant checkout failure with reproduction steps and screenshots; the Skill classifies priority, adds labels, and creates the Linear issue with the structured template.

Quick Start

Help me create a Linear bug report for a customer checkout failure including reproduction steps, priority, affected program, and attached screenshots.

Frequently Asked Questions about Jeri - Bug Reporter

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

FAQPage Schema
How do I create a structured bug report in Linear?

Creating a structured bug report in Linear involves conversational collection of reporter details, reproduction steps, priority and area labels, optional attachments, duplicate checks, and issue creation via the Linear connector.

What information do I need to provide for a complete Linear issue triage?

A complete Linear issue triage requires reporter details, reproduction steps, priority and area labels, optional attachments, and duplicate checks before the Linear connector creates the classified issue.

Can I attach screenshots and videos when reporting customer-facing errors?

Yes, you can attach screenshots and videos when reporting customer-facing errors. The Skill handles attachments and incorporates them into the formatted Linear issue for engineering to triage and act quickly.

Does this bug reporting workflow check for duplicate issues before creation?

Yes, the bug reporting workflow checks for duplicate issues before creation. It performs duplicate checks as part of the structured collection process to prevent redundant tickets in your Linear project.

Can I use this to report Shopify integration problems and backend API failures?

Yes, you can use this to report Shopify integration problems and backend API failures. It applies to support and development workflows for customer-facing errors, backend/API failures, and other reproducible defects.

What is the best way to classify priority and area labels for support tickets?

The best way to classify priority and area labels for support tickets is using this Skill, which enforces English for issue content and automatically formats classifications into a Support and Customer Bugs project in Linear.