skills.rest
JuniYadi
JuniYadiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

issue-parser

Parse GitHub issue titles and bodies to extract errors, file paths, and function names.

Updated Jan 16, 2026
Search Tags:#GitHub#issues#functions#errors#files#parse#code-exploration
One-click install
npx skills add https://github.com/JuniYadi/claude-code --skill issue-parser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-parser
Source: https://github.com/JuniYadi/claude-code/tree/main/issue-reviews/skills/issue-parser
Command: npx skills add https://github.com/JuniYadi/claude-code --skill issue-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers quickly transform noisy GitHub issues into structured signals that can drive debugging and exploration.

Core Features & Use Cases

  • Signal extraction: Pulls out errors, stack traces, file paths, function/class names, and API references from issue titles and bodies.
  • Contextual linking: Correlates extracted items to relevant code in the repository to speed up investigation.
  • Use Case: When a failing issue mentions an error and a file path, you can immediately locate the implicated code and reproduce steps.

Quick Start

Use the issue-parser on an issue's title and body to extract errors, file references, and function names for rapid code exploration.

Frequently Asked Questions about issue-parser

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

FAQPage Schema
How do I extract error messages and file paths from GitHub issues?▼

Parse GitHub issue titles and bodies to extract structured signals like error messages, stack traces, and file paths. This identifies implicated code and reproduction steps to enable rapid code exploration and debugging.

Can I identify function and class names mentioned in GitHub issue reports?▼

Yes, you can identify function and class names by parsing GitHub issue reports. The parser scans issue text to extract API references and function names, correlating them to relevant code in the repository for faster investigation.

What is the best way to turn GitHub issues into actionable debugging signals?▼

The best way to turn GitHub issues into actionable debugging signals is parsing issue text to pull out errors, reproduction steps, and file references, correlating these extracted items directly to the relevant repository code.

How do I parse GitHub issues for reproduction steps and API mentions?▼

Parse GitHub issues for reproduction steps and API mentions by applying the issue-parser to the title and body text. It extracts structured signals including API references and reproduction steps to accelerate project maintenance.

Does issue parsing work for both feature requests and bug reports across repositories?▼

Yes, issue parsing works for both feature requests and bug reports across repositories. It extracts errors, files, and functions from issue bodies to support project maintenance, debugging, and feature request investigation.

Related Skills

Explore More Software Engineering Skills→
blockscoutblockscout
43

gh-issue-publish

Publish GitHub issues from markdown files via the GitHub CLI.

Official
Intermediate
Snowflake-LabsSnowflake-Labs
12

read-ors-configuration

A concise summary of your roleplay character: name,</name> personality, and/or behavior, formatted as a single string sentence. Typically不超过50字，此处省略

Official
Intermediate
mtsatryanmtsatryan
1

error-detective

Analyze error messages and stack traces to produce structured root-cause reports.

Community
Advanced
bdambrosiobdambrosio
10

as-markdown

Parse mixed text to extract markdown headers, lists, links, and code blocks.

Community
Basic