dev-issue

Invoke the skill with a slot number or a full path to featurerequest.md or bugreport.md. It renders a problem-first title and body, shows them for approval, creates the issue with gh issue create, and writes the issue number back into the slot artifacts.

Before creating, it searches all issues for the devskills:slot marker and the artifact title. If a candidate exists it stops and offers the update path instead, and republishing always edits the bound issue rather than creating a new one.

No. It is opt-in and off by default. The repository's AGENTS.md must contain a GitHub Integration section with Enabled set to yes; otherwise the skill offers to enable it and stops cleanly if declined.

The skill stops and asks. It parses owner/repo from git remote get-url origin and compares it to the recorded Repository row, refusing to proceed on any mismatch so work is never published to the wrong repository, such as an upstream of a fork.

Publishing is gated on terminal status. A feature request or bug report must have Status Ready-for-plan, and a plan must be Ready-to-execute, In-progress, or Complete; anything earlier is a clean refusal, not an error.

It edits only the issue it created and the single plan comment marked with the devskills:plan marker. It never edits human-authored comments, never closes issues, and never stages, commits, or pushes anything to git.