create-issuelisted

<!-- requires: explorer --> <!-- chains: none --> <!-- generated from .ai/workflows/create-issue.md; do not edit directly --> > **Codex:** this skill is the `/create-issue` adapter. Use Codex role agents from `.codex/agents/` when the runtime exposes them; otherwise perform the work directly and keep the same structured output. > Codex does not substitute `$ARGUMENTS` — read it as the arguments given in the user's request. Create a GitHub issue for: $ARGUMENTS Follow these steps: 1. **Detect repo**: Run `git remote get-url origin` from the current directory to identify the target repo. If `--repo owner/repo` is provided in $ARGUMENTS, use that instead. 2. **Research**: Explore relevant files (use explorer role agent for broad searches) to understand the affected code area. This ensures accurate acceptance criteria. 3. **Draft the issue**: - **Title**: Short, imperative ("Fix token refresh race condition") - **Problem**: 2-3 sentences describing what's broken or missing and its impact - **Acceptance Criteria**: Bulleted checklist of testable conditions for "done" - **Technical notes**: Relevant file paths, functions, or architecture context from your research - **Labels**: determine appropriate labels (bug / enhancement / frontend / backend). Run `gh label list --repo <detected-repo>` first — only use labels that actually exist in the repo. 4. **Create it**: Run `gh issue create` with `--label` for each applicable label. Use a heredoc for the body: ``