issue

Analyze codebase impact and create GitHub issues via gh issue create.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/sr-ai-dev/sr-harness --skill issue-sr-ai-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/sr-ai-dev/sr-harness/tree/main/skills/issue
Command: npx skills add https://github.com/sr-ai-dev/sr-harness --skill issue-sr-ai-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The issue skill prevents guesswork in GitHub issue creation by first analyzing how a user’s request affects the codebase, then packaging the result into a structured issue with clear confidence boundaries.

Core Features & Use Cases

  • Full impact analysis before writing the issue: explores related code, dependencies, test coverage, and relevant history using parallel investigation.
  • Confidence-based issue sections: separates findings into ✅ AI Verified, 🤔 Decision Required, and ⚠️ Human Verify so stakeholders know what’s safe vs. what needs review.
  • Preview and user confirmation guardrails: requires explicit confirmation before running gh issue create, and allows an edit-then-create loop.
  • Request preservation: keeps the user’s original /issue text verbatim inside the “Request” section for traceability.

Quick Start

Run /issue with a clear description of the change or bug you want to report, then confirm the generated preview to create the GitHub issue.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I create a GitHub issue with impact analysis for my codebase?

To create a GitHub issue with impact analysis, this skill investigates related files, dependencies, and test coverage before drafting the issue text. It then separates findings into AI Verified, Decision Required, and Human Verify categories for clear confidence boundaries.

What is codebase impact analysis and when do I need it for issue creation?

Codebase impact analysis examines related code, dependencies, test coverage, and history to determine the effects of a proposed change. You need it for issue creation when filing bug reports, feature requests, or investigations to prevent guesswork and ensure stakeholders understand the scope.

Can I review and edit a generated GitHub issue before it is created?

Yes, you can review and edit a generated GitHub issue before it is created. The skill requires explicit user confirmation after presenting a preview, allowing an edit-then-create loop before executing the gh issue create command.

Does this issue creation workflow require the GitHub CLI to run?

Yes, this issue creation workflow requires the GitHub CLI to run. The skill ultimately creates the issue on your repository using the gh issue create command after you confirm the generated preview.

What's the best way to document decision required and human verify findings in a bug report?

The best way to document decision required and human verify findings in a bug report is using confidence-based sections. The skill separates findings into AI Verified, Decision Required, and Human Verify categories so stakeholders know what is safe versus what needs manual review.