github-issue-createlisted

# GitHub Issue Create ## Safety contract - Always create a dry-run plan before creating an Issue. - Never apply without explicit approval of owner/repo, title, body, labels, assignee, Project, Status, and Priority. - Fail closed on identity changes, target mismatch, stale plans, missing labels, ambiguous Project fields, or permissions. - Never infer and write Priority from prose alone. Present an inferred value as a proposal and require explicit approval. - On partial failure, resume the existing Issue; never create a replacement automatically. - Apply repository-specific Issue policy when one exists. This skill must not invent routing or labels. - `--confirm-target` prevents repository mix-ups; it does not prove human approval. Human approval remains a host-level interaction requirement. The content-derived `plan_id` rejects edits to the approved title, body, labels, fields, or operations. ## Prerequisites - Install the complete `github-operations` plugin. A copied skill directory is intentionally unsupported. - Require Python 3.11+, `gh`, and an explicit config or `.agents/github-operations.json`. - When using an explicit config from another installed resource, resolve that file to an absolute path and pass it with `--config`. ## Workflow Resolve `scripts/run.py` against this skill directory before executing it. 1. Draft the Issue using the target repository's `AGENTS.md`, templates, language, and available labels. 2. Write a long body to a temporary file outside the