gentle-ai-issue-creation

1# Issue Creation
2 
3## Core Rule
4 
5Discover the target repository's contribution workflow before proposing or publishing. YAML Issue Forms are the format authority for the default automated path: materialize reviewed answers into a private `BODY_FILE` and publish with `--body-file`.
6 
7## Safe Discovery
8 
9Before any `gh auth status` or target read, require explicit human authorization for the remote destination (exact host and repository), operation (including discovery and intended issue creation), and credential/session to use. A local checkout is not authorization. If any is missing or ambiguous, stop locally; never probe credentials or sessions to resolve ambiguity. Run the checks below only with the authorized credential/session against the authorized destination; if `gh auth status` would inspect other credentials/sessions, do not run it. Verify the discovered `REPO`, `HOST`, and `TARGET` match the authorized destination before continuing; never switch identities or targets implicitly.
10 
11After that gate, run read-only checks:
12 
13```bash
14gh auth status
15REPO="$(gh repo view --json nameWithOwner -q .nameWithOwner)"
16REPO_URL="$(gh repo view --json url -q .url)"
17HOST="${REPO_URL#*://}"
18HOST="${HOST%%/*}"
19TARGET="$HOST/$REPO"
20gh repo view --json nameWithOwner,url,hasDiscussionsEnabled,hasIssuesEnabled,isBlankIssuesEnabled
21git ls-files README.md CONTRIBUTING.md CONTRIBUTING.* .github/CONTRIBUTING.md .github/ISSUE_TEMPLATE .github/ISSUE_TEMPLATE/config.yml
22…