/as:studio-feedback — Prepare a GitHub report

Harness note: use /as:<skill> on Claude Code and $<skill> on Codex. Resolve <skill-root> as the directory containing this loaded SKILL.md and <plugin-root> as the plugin root that contains skills/, and use equivalent native tools when host tool names differ.

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:

• Bug: bug-report.yml, label bug; fields version, os, skill, what-happened, expected.
• Feature: feature-request.yml, label enhancement; fields version, skill, problem, proposal.

2. Prepare minimal fields locally

Read the installed version from <plugin-root>/.codex-plugin/plugin.json on Codex or <plugin-root>/.claude-plugin/plugin.json on Claude Code. Gather the operating-system name and version with local commands only. Infer the affected skill from the conversation when reliable; otherwise leave it blank or ask during editing.