github-create-issue

Core principles

1. Objectivity is the signal. Avoid phrases like "looks good." Show impact scope and estimated difficulty in concrete terms.
2. Never upload without user confirmation. Show the exact final form (title, body, labels, repo) and get explicit approval before publishing.

Workflow

There are decision points between steps where user input is needed — don't try to do everything at once.

Throughout: use repo context (git log, branch names, existing issues, labels) to infer conventions before defaulting or asking the user. The repo usually answers most "how should this look?" questions — language, prefix style, body structure, label vocabulary.

1. Confirm intent (ask back if unclear)

Check that all four are clear enough: