github-issue-context-reader

Read GitHub issue context and comments to generate a structured task delta.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ai212983/gh-csi --skill github-issue-context-reader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-context-reader
Source: https://github.com/ai212983/gh-csi/tree/main/skills/github-issue-context-reader
Command: npx skills add https://github.com/ai212983/gh-csi --skill github-issue-context-reader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read issue context without mutating GitHub state to quickly generate a structured task delta for planning and execution.

Core Features & Use Cases

  • Resolve an issue reference from a number or URL and extract the latest comments.
  • Produce a compact task delta describing added, modified, and unresolved items.
  • Guardrails ensure no changes are made to the GitHub issue during analysis; suitable for planning, review, and scope understanding.

Quick Start

Summarize the active GitHub issue and its comments to produce a structured task delta.

Frequently Asked Questions about github-issue-context-reader

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

FAQPage Schema
How do I extract a structured task delta from GitHub issue comments for planning?

To extract a task delta from a GitHub issue, read the issue context and comments to generate a compact summary of added, modified, and unresolved items without mutating the original issue state.

What is a task delta in GitHub issue scope discussions?

A task delta in GitHub issue scope discussions is a structured summary identifying added, modified, and unresolved items derived from reading issue context and comments to clarify planning and execution steps.

Can I analyze GitHub issue context without modifying the issue state?

Yes, you can analyze GitHub issue context without modifying state by using guardrails that ensure no changes are made to the issue during review, making it suitable for safe scope understanding.

How do I summarize GitHub issue comments to identify unresolved items?

Summarize GitHub issue comments by resolving the issue reference from a number or URL, extracting the latest discussions, and producing a structured delta of added, modified, and unresolved items.

Does the GitHub issue context reader work with issue URLs or just issue numbers?

The issue context reader resolves references from both a GitHub issue number or a direct URL, extracting the latest comments to produce a structured task delta for review and planning.