Agent skill

Issue Create

by icebear0828 in icebear0828/codex-proxy

Interview the user to gather all required context, then open a high-quality GitHub issue (gh issue create) on the codex-proxy repo with the right template, labels, and structured body.

Custom licenceAuto-check: notesDevelopment

Install Issue Create

skills CLI
$ npx skills add icebear0828/codex-proxy --skill issue-create -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install icebear0828/codex-proxy issue-create --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/icebear0828/codex-proxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/issue-create .claude/skills/issue-create && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
issue-create
GitHub stars
1.8k
Token cost
~1.8k tokens
SKILL.md length
931 words
Files
7 (incl. references, assets)
Skills in repo
3
Repo updated
First seen
Licence
Custom licence

At a glance

Interview the user to gather all required context, then open a high-quality GitHub issue (gh issue create) on the codex-proxy repo with the right template, labels, and structured body.

  • Works in 4 steps: Type classification → Required-field interview → Code & related-context grounding → …
  • : user says open an issue
  • SKILL.md covers Overview, When to Use, Important Rules and Key Workflows, plus 1 more section
  • Calls gh and npm

What it does

Issue Create is an agent skill from icebear0828/codex-proxy. Interview the user to gather all required context, then open a high-quality GitHub issue (gh issue create) on the codex-proxy repo with the right template, labels, and structured body. TRIGGER when: user says "open an issue", "file an issue", "create issue", "report a bug", "feature request", "提个 issue", "报 bug", "提需求". DO NOT TRIGGER when: user wants to view, search, comment on, or close existing issues (use gh issue list/view/comment/close directly); user is writing a PR description (use pr-push).

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files and assets (for example `assets/bug-report.md`, `assets/feature-request.md` and `assets/perf-report.md`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: OpenAI-compatible proxy for ChatGPT Codex Responses API.

When your agent uses it

  • : user says open an issue
  • Feature request
  • : user wants to view
  • Close existing issues (use gh issue list/view/comment/close directly)

Example prompts

  • “open an issue”
  • “file an issue”
  • “create issue”
  • “/issue-create”

Requirements

  • Docker
  • Pre-approved tools (allowed-tools): Bash, Read, Write

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Type classification
  2. Required-field interview
  3. Code & related-context grounding
  4. Render, confirm, submit

What it can do on your machine

Read from SKILL.md and the folder at commit fb946da. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Issue Create loads about 1.8k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 131 tokens; SKILL.md has 931 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~131
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 931 words (~1,841 tokens).

“Gather complete context through a structured interview, then file a well-formed issue. The interview is a hard gate — vague issues waste maintainer time.”

— opening of SKILL.md by icebear0828, Custom licence
name
issue-create
allowed-tools
Bash, Read, Write

Read the full SKILL.md on GitHub

Files

SKILL.md and 6 other files (references, assets) in .agents/skills/issue-create of icebear0828/codex-proxy.

  • SKILL.md
  • assets/bug-report.md
  • assets/feature-request.md
  • assets/perf-report.md
  • assets/question.md
  • references/issue-types.md
  • references/labels.md

Open the folder on GitHubat commit fb946da

Compare with similar skills

Issue Create next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Issue Create compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issue Create this skillicebear0828/codex-proxy1.8k—~1.8kAutomated safety check: NotesCustom licence
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from icebear0828/codex-proxy

  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.2k tokensUpdated today
    Auto-check: notes
  • PR Push

    icebear0828/codex-proxy

    Package the current working changes into a standards-compliant codex-proxy pull request: branch hygiene, commit message linting, CHANGELOG prompt, conventional commit, push, and gh pr create against…

    1.8k GitHub stars~2.3k tokensUpdated today
    Auto-check: notes

Works with

Categories

Questions about Issue Create

What does Issue Create do?

Interview the user to gather all required context, then open a high-quality GitHub issue (gh issue create) on the codex-proxy repo with the right template, labels, and structured body. Issue Create is an agent skill from icebear0828/codex-proxy. Interview the user to gather all required context, then open a high-quality GitHub issue (gh issue create) on the codex-proxy repo with the right template, labels, and structured body.

When should I use Issue Create?

Issue Create fits situations like: : user says open an issue; feature request; : user wants to view; close existing issues (use gh issue list/view/comment/close directly).

How do I install Issue Create in Claude Code?

Run `npx skills add icebear0828/codex-proxy --skill issue-create -a claude-code`. Or copy the skill folder (.agents/skills/issue-create in icebear0828/codex-proxy) into .claude/skills/issue-create in your project. Claude Code loads it when a task matches its description.

How do I install Issue Create in Codex?

Run `npx skills add icebear0828/codex-proxy --skill issue-create -a codex`. Or copy the skill folder (.agents/skills/issue-create in icebear0828/codex-proxy) into .agents/skills/issue-create in your project. Codex loads it when a task matches its description.

Can I use Issue Create in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add icebear0828/codex-proxy --skill issue-create -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/issue-create, .gemini/skills/issue-create, .github/skills/issue-create and .opencode/skills/issue-create in your project.

What does Issue Create need to run?

Going by SKILL.md and its folder, Issue Create needs the command-line tools its instructions call (gh and npm). Our summary lists: Docker. Its frontmatter pre-approves these tools: Bash, Read, Write.

Does Issue Create access the network?

SKILL.md contains no URLs. Its commands use gh and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Issue Create safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Issue Create use?

Issue Create has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Issue Create use?

About 1.8k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Issue Create?

Skills that share tags, products or a category with Issue Create: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Create?

icebear0828 (a GitHub user) maintains it in icebear0828/codex-proxy, which has 1,805 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.

Source: icebear0828/codex-proxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.