skills.rest
noni2she
noni2sheCOMMUNITY
Explore all skills by this author →
GitHub

issue-extract

Convert Jira and GitHub issue JSON into a unified pipeline schema.

1|Updated Apr 9, 2026
Search Tags:#jira#attachments#issue-tracker#github-issues#bug-reproduction#data-mapping#json-normalization
One-click install
npx skills add https://github.com/noni2she/agent-fix --skill issue-extract-noni2she
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: issue-extract
Source: https://github.com/noni2she/agent-fix/tree/main/skills/issue-extract
Command: npx skills add https://github.com/noni2she/agent-fix --skill issue-extract-noni2she

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Raw issues from Jira or GitHub come in different JSON schemas, making downstream bug-fix workflows hard to automate. This Skill converts heterogeneous issue tracker payloads into a single, consistent set of fields so later pipeline steps can operate reliably.

Core Features & Use Cases

  • Source detection for common trackers: Identifies Jira issues vs GitHub Issues based on distinctive JSON shapes, otherwise returns an error.
  • Field mapping into a unified schema: Produces standardized fields like issue_id, summary, module, description, reproduction_steps, expected, actual, attachments, and comments.
  • Attachments and comments handling: Extracts attachment/video/document URLs (no downloads) and supports comment collection expectations per the input data availability.
  • Use case: Turn a Jira issue JSON export or a GitHub issue webhook payload into the canonical format required by an automated extract/analyze/implement/test pipeline.

Quick Start

Provide the raw issue JSON as input so the Skill outputs exactly one fenced json block containing the standardized fields.

Frequently Asked Questions about issue-extract

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

FAQPage Schema
How do I normalize Jira and GitHub issue JSON into a unified schema for automated pipelines?▼

Normalize issue tracker JSON by feeding raw Jira or GitHub payloads into a parser that maps identifiers, module hints, and reproduction fields into a deterministic unified schema. This outputs standardized JSON containing required keys like issue_id, summary, and reproduction_steps.

What happens to unmapped fields when converting raw issue tracker data to a standard format?▼

Unmapped fields during issue JSON normalization are handled by inserting placeholders into the deterministic output. This ensures downstream bug-fix workflows receive a consistent schema with all required keys present, even if the original Jira or GitHub payload lacks specific structured data.

Does issue JSON normalization support extracting attachments and comments from Jira and GitHub?▼

Issue JSON normalization supports extracting attachment URLs, videos, and documents from Jira and GitHub payloads without downloading files. It also collects comments based on input data availability, mapping them into the unified pipeline schema alongside structured reproduction and expectation fields.

Can I use this to parse issue tracker payloads from sources other than Jira and GitHub Issues?▼

Parsing issue tracker payloads from unknown sources is not supported. The normalization process detects specific Jira and GitHub JSON shapes to map fields correctly; if the source is unrecognized, it returns an error object instead of attempting an unreliable conversion.

Why does my automated bug-fix workflow fail when processing heterogeneous issue exports?▼

Automated bug-fix workflows fail because Jira and GitHub issue exports use different JSON schemas. Normalizing these heterogeneous payloads into a single consistent set of fields allows later pipeline steps to operate reliably without encountering unexpected missing or misaligned data keys.

Related Skills

Explore More Software Engineering Skills→
lutzcc1lutzcc1

implementation-plan-writer

Generate a structured implementation plan document from a tracker issue.

Community
Advanced
agentjidoagentjido
48

demo-unit-converter

Convert temperature and distance inputs into standardized units for downstream workflows.

Official
Intermediate
microwindmicrowind
65

JSON验证器

Validate and format JSON data with syntax, structural, and optional schema checks.

Official
Advanced
thecloudtipsthecloudtips
18

Data Extraction

Extract and normalize data from CSV, JSON, text, Notion, and Google Drive sources.

Community
Advanced