issue-creation

1# Issue Creation
2 
3## Activation Contract
4 
5Use this portable skill for drafting, creating, commenting on, triaging, or approving GitHub issues. The destination repository's issue format policy is authoritative: use its selected form or template, or its supported no-template path.
6 
7## Hard Rules
8 
9- Reuse verified current-session facts; discover only missing or stale facts.
10- Before any needed target policy read or write, resolve the exact target as `[HOST/]OWNER/REPO`. Never assume the current repository.
11- Follow the target's supported issue format. Never bypass a required form with Markdown or a blank body. A verified no-template policy is not a missing required form. Never use an alternate publisher or a browser route as a fallback.
12- Complete one open-and-closed duplicate search before a write. Reuse that result while it remains current.
13- Never invent facts, selections, affirmations, labels, approval, or policy; ask for the smallest missing fact.
14- Create-time labels are limited to labels declared by the selected form or template, or labels permitted by repository policy when no template exists; all must be discovered to exist and permitted for the actor.
15- Before ANY post-publication workflow mutation, read `references/delegated-workflow-actions.md` completely and follow it. It is normative, not optional background.
16…