Individual skill
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
internal/assets/skills/issue-creation/SKILL.md
Source commit 55240afb100ad6d2ef5fbe16f7be33a7693f77ad
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 8,585
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- claude-code Repository topic
- code-review Repository topic
- copilot Repository topic
- cursor Repository topic
- developer-tools Repository topic
- golang Repository topic
- llm Repository topic
- mcp Repository topic
- opencode Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Issue Creation
## Activation Contract
Use 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.
## Hard Rules
- Reuse verified current-session facts; discover only missing or stale facts.
- Before any needed target policy read or write, resolve the exact target as `[HOST/]OWNER/REPO`. Never assume the current repository.
- 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.
- Complete one open-and-closed duplicate search before a write. Reuse that result while it remains current.
- Never invent facts, selections, affirmations, labels, approval, or policy; ask for the smallest missing fact.
- 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.