dev-issue

Publishes slot feature requests and bug reports as GitHub issues via gh CLI.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-issue-ginocanessa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-issue
Source: https://github.com/GinoCanessa/dotnet-fhir-packages/tree/main/.github/skills/dev-issue
Command: npx skills add https://github.com/GinoCanessa/dotnet-fhir-packages --skill dev-issue-ginocanessa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a locally authored feature request or bug report into a GitHub issue by hand risks duplicate issues, wrong repositories, and lost synchronization between the local artifact and the published issue. This Skill automates that publishing step with strict safeguards. ## Core Features & Use Cases - Duplicate-safe issue creation: Searches existing issues by slot marker and title before creating, so an interrupted run never produces a second issue. - Idempotent issue updates: Re-renders the title and body from the refined local artifact and edits the existing issue in place, never creating a new one. - Managed plan comment: Attaches a finalized plan.md as exactly one marker-tagged comment that is updated in place, leaving human-authored comments untouched. - Use Case: After finishing a bug report in scratch/0423-02/bugreport.md, invoke the skill with slot number 2 to publish it as a labeled GitHub issue and record the issue binding back into the slot artifacts. ## Quick Start Publish the feature request in today's slot 2 as a GitHub issue using the dev-issue skill.

Frequently Asked Questions about dev-issue

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

FAQPage Schema
How do I publish a feature request as a GitHub issue from the command line?

Provide the slot number or full path to the featurerequest.md artifact, and the skill renders a title and problem-first body, then creates the issue with gh issue create after your approval. The issue number is written back into the artifact's Issue row.

How do I update an existing GitHub issue after refining a bug report?

Re-run the skill on the same slot; it detects the recorded issue number, re-renders the title and body from the local artifact, shows a diff against the current issue, and applies the edit with gh issue edit. It never creates a second issue.

Does this skill work without the GitHub CLI installed?

No. The skill requires gh to be installed and authenticated; it runs gh --version and gh auth status as preconditions and stops with the exact error if either fails. There is no unauthenticated fallback.

What happens if GitHub integration is not enabled in AGENTS.md?

The skill is opt-in and off by default. If AGENTS.md lacks a GitHub Integration section or Enabled is set to no, it offers to enable the integration through the Resolve-and-Record Protocol and otherwise stops cleanly without writing anything.

Why does the skill refuse to publish my artifact?

Publishing is gated on terminal status: a feature request or bug report must have Status set to Ready-for-plan, and a plan must be Ready-to-execute, In-progress, or Complete. Earlier statuses produce a clean refusal naming the required status.

Can the skill close or delete GitHub issues?

No. The skill never closes issues; closing is a human decision or a merge-time side effect of a pull request's Closes #N reference. It also never edits or deletes comments lacking its managed marker.