/as:studio-feedback — Prepare a GitHub report

Before acting, read the host contract and this component's declaration (skill:studio-feedback). Load only its referenced mode profiles from the shared catalog. Compose modes required by the actual task; declarations are requirements, not proof of access or permission.

Host adapter: read delivery-specific guidance for invocation, metadata access, questions and browser opening.

This native report-preparation procedure has no registered operation IDs. Its steps below are the complete owner; no Arch Studio runner, installer, executable download or reconstructed helper is required. An ordinary native encoding or metadata tool may be used where available. Follow the completion contract and distinguish a prepared draft, an opened URL and a submitted issue.

Prepare a report locally, show exactly what would leave the machine, and open GitHub only after one informed confirmation. Never submit the issue, post a comment, call the GitHub API, or transmit diagnostics in the background.

1. Choose the report type

Infer bug or feature when the request is clear. Otherwise use one AskUserQuestion gate to choose the type; do not first ask the same question in prose.

Use these issue forms and labels: