skills.rest
frumu-ai
frumu-aiOFFICIAL
Explore all skills by this author →
Website𝕏@frumu_aiGitHub

github-issue-reporter

Convert production incident summaries into structured GitHub issues with deduplication.

114|13|Updated Jan 17, 2026
Search Tags:#automation#github#issues#alerts#incidents#bug tracking
One-click install
npx skills add https://github.com/frumu-ai/tandem --skill github-issue-reporter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-issue-reporter
Source: https://github.com/frumu-ai/tandem/tree/main/resources/skill-templates/github-issue-reporter
Command: npx skills add https://github.com/frumu-ai/tandem --skill github-issue-reporter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of actionable GitHub issues directly from production incidents, streamlining the bug tracking and resolution process.

Core Features & Use Cases

  • Incident to Issue Conversion: Automatically transforms raw incident summaries into well-structured GitHub issues.
  • Deduplication: Checks for existing open issues to prevent duplicates.
  • Use Case: When a critical error is detected in production, this Skill can automatically create a GitHub issue in the relevant repository, assign it to the appropriate team, and include all necessary details for immediate investigation.

Quick Start

Use the github-issue-reporter skill to create a GitHub issue from the latest incident summary in the 'my-org/my-repo' repository.

Frequently Asked Questions about github-issue-reporter

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

FAQPage Schema
How do I automatically create GitHub issues from production incidents?▼

To automatically create GitHub issues from production incidents, this Skill transforms raw incident summaries into structured GitHub issues. It requires the incident summary and the target repository name to generate a tracking entry for immediate investigation.

How does incident to issue conversion handle duplicate bug tracking entries?▼

Incident to issue conversion handles duplicate bug tracking entries by checking for existing open issues in the target repository before creating a new one. This deduplication prevents redundant alerts from generating multiple GitHub issues for the same incident.

Can I trigger GitHub issue creation from production error alerts?▼

You can trigger GitHub issue creation from production error alerts by passing the alert summary to this Skill. It processes the incident data and uses web fetching and issue creation tools to log the bug directly in the specified GitHub repository.

What inputs are required to convert an incident alert into a GitHub issue?▼

Converting an incident alert into a GitHub issue requires specific inputs: a detailed incident summary and the target repository identifier. The Skill uses these to fetch existing repository data and automate the structured issue creation.

What is the best way to automate bug tracking from production alerts in GitHub?▼

The best way to automate bug tracking from production alerts in GitHub is using a Skill that parses incident summaries and deduplicates against open issues. This ensures structured, actionable bug reports are created automatically without manual entry.

Related Skills

Explore More Software Engineering Skills→
enowdevenowdev
13

slack-bot

Send text and Block Kit messages to Slack channels via Incoming Webhooks or the Web API.

Community
Intermediate
lotosbinlotosbin
14

task-manager

Manage agent tasks by creating and updating GitHub Issues with labels and milestones.

Community
Intermediate
opendatahub-ioopendatahub-io

pipeline-grouping

Group and deduplicate CI/CD pipeline failures using error files and Jira tickets.

Official
Intermediate
dyzsasddyzsasd
5

ops-agent

Poll production endpoints and logs to detect service degradations and file bug tickets.

Community
Advanced