AGENT SKILL

issue

Create GitHub issues from the user's current request or conversation context. Resolve the target repository from the local checkout or explicit owner/repo, inspect existing labels, infer a suitable issue type label when possible, and create the issue using native GitHub tooling. Use when the user invokes /issue or $issue, asks to create/open/file a GitHub issue, or describes work that should be captured as an issue from a local GitHub repository checkout.

License 许可
MIT
最近更新
2026-07-19
Stars
★ 1
Forks
1

01 前言 Front Matter

name
issue
metadata
{ "source": "Codex 'issue' skill (ported 2026-05-24)", "short-description": "Create well-formed GitHub issue from context, using existing repo labels" }
description
Create GitHub issues from the user's current request or conversation context. Resolve the target repository from the local checkout or explicit owner/repo, inspect existing labels, infer a suitable issue type label when possible, and create the issue using native GitHub tooling. Use when the user invokes /issue or $issue, asks to create/open/file a GitHub issue, or describes work that should be captured as an issue from a local GitHub repository checkout.
when-to-use
User describes a bug, feature request, documentation task, maintenance item, or research/validation work and wants it turned into a properly labeled GitHub issue in the current repo (or a specified one). 'file an issue for this', 'create a GitHub issue', 'open an issue about the regression in X'.
allowed-tools
[ "run_terminal_cmd", "read_file", "grep", "list_dir", "grok_com_github", "ask_user_question", "web_search" ]
argument-hint
[owner/repo or URL] <description of the issue>

03 SKILL.md 正文

GitHub Issue (Grok Port)

Overview

Create one GitHub issue from the user's description, using the current local checkout to resolve the repository when possible. Use existing repository labels only, infer the issue type when the evidence is clear, and ask before creating the issue when repository or label choice is ambiguous.

Prefer the connected grok_com_github MCP tools for all GitHub operations (schema discovery first if tool names are not yet known in the session). Fall back to gh CLI via run_terminal_cmd only when the MCP is unavailable or insufficient for the required action.

Workflow

  1. Resolve the repository

    • If the user provided an explicit owner/repo or GitHub repository URL, use it.
    • Otherwise, from the current working directory, run git rev-parse --show-toplevel (via run_terminal_cmd) to find the repo root.
    • If not inside a Git repository, ask for the target repository in owner/repo form using ask_user_question.
    • Run git remote -v and collect GitHub remotes only.
    • Normalize to owner/repo form.
    • If exactly one GitHub repository is present, use it. If multiple, prefer origin only when all origin GitHub URLs agree; otherwise ask which repository to use via ask_user_question.
    • Once resolved, confirm the full name (e.g. "velocityworks/prime-gap-structure").
  2. Draft the issue

    • Derive a concise title from the user's request.
    • Write a Markdown body that preserves the concrete facts the user supplied.
    • Do not invent reproduction steps, expected behavior, versions, files, screenshots, acceptance criteria, or implementation details.
    • If the request does not contain enough information to identify the issue, ask one direct question before creating it (use ask_user_question).
  3. Inspect existing labels (via MCP or gh)

    • Preferred: use grok_com_github tools (after schema discovery if needed) to list labels for the repository.
    • Fallback: run_terminal_cmd with gh label list --repo OWNER/REPO --json name.
    • If labels cannot be inspected, state that plainly and ask whether to create the issue without labels or provide exact label names.
    • Never create new labels unless the user explicitly asks.
  4. Infer the issue type from the request and the existing labels

    • Bug language: bug, broken behavior, regression, crash, failure, exception, error.
    • Feature language: feature, enhancement, capability, support, add, implement.
    • Documentation language: docs, documentation, README, explanation, guide, tutorial.
    • Maintenance language: refactor, cleanup, internal improvement, maintenance, tech debt.
    • Research language: research, experiment, benchmark, validation, measurement.
    • Apply only existing labels whose names match the inferred type or a clear local synonym.
    • If confidence is low or several label choices are equally plausible, ask the user to choose before creating the issue using ask_user_question.
  5. Create the issue

    • Preferred path: use the appropriate grok_com_github MCP tool for issue creation (e.g. issue_write or equivalent after discovering the exact schema and parameter names via the MCP discovery step).
    • Fallback: gh issue create --repo OWNER/REPO --title "..." --body "..." --label "..." via run_terminal_cmd.
    • Do not assign users or set a milestone unless the user explicitly requested it.
    • Do not use update tools to replace labels after creation unless correcting a mistake in the same workflow.
  6. Return the result

    • Include the issue number, URL, title, and labels applied.
    • Include a short body summary when the body is more than a few lines.
    • If no labels were applied, say Labels: none.
    • Use the compact output shape below.

Label Selection Rules (preserved)

Prefer exact label names already present in the repository. If a repository has both broad and narrow labels that fit, choose the narrow issue-type label only when the request clearly names that category; otherwise ask.

Common mappings:

  • bug, regression, or a clear local equivalent for broken behavior.
  • enhancement, feature, or a clear local equivalent for new capability work.
  • documentation, docs, or a clear local equivalent for documentation work.
  • refactor, maintenance, tech debt, or a clear local equivalent for internal cleanup.
  • research, experiment, benchmark, or a clear local equivalent for research or validation work.

When the repository has no suitable existing label for the inferred type, create the issue without that label and report that no matching existing label was available.

Output Format

Use this compact shape:

Created issue:
- Repo: OWNER/REPO
- Issue: #NUMBER TITLE
- URL: https://github.com/OWNER/REPO/issues/NUMBER
- Labels: label-a, label-b

Grok-Specific Adaptations

  • MCP First: The connected grok_com_github server (with its 45+ tools including issue_write, list_issues, search_issues, get_label, etc.) is the idiomatic integration point. Always attempt MCP schema discovery (call tool ... or the documented MCP bootstrap) before guessing tool names.
  • Local checkout as context: The git-based repo resolution is preserved because it gives the user a frictionless "just file it for the project I'm in" experience.
  • ask_user_question: Used for any interactive choice (repo selection, label selection, confirmation of low-confidence inference).
  • No label invention: Strict.

Success Criteria

  • The created issue URL is returned.
  • Labels (if any) are exactly from the repository's existing set.
  • The body is a faithful capture of the user's stated facts with zero invention.
  • The user sees a clear, copy-pasteable record of what was created.

Stop Conditions

  • No usable GitHub authentication (neither MCP nor gh).
  • User has not supplied enough information and clarification questions have been exhausted.
  • The user explicitly says "don't create the issue yet" or similar.

This port maintains the original's disciplined use of existing labels and faithful capture while routing all GitHub mutations through Grok's native MCP surface where possible.

04 同仓库更多 Skills

zfifteen
zfifteen/skills-catalog

Zotero

Use Zotero Desktop from Codex to enable/probe the local API, search a local Zotero library, list items/collections/tags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX/RIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.

★ 1
zfifteen
zfifteen/skills-catalog

zoom-apps-sdk

Use when using Apps SDK.

★ 1
zfifteen
zfifteen/skills-catalog

youtube

Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript. Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or "what does this video actually say". The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content. Triggers: "youtube transcript", "get the transcript of this video", "summarize this youtube video", "what did they say in https://youtube.com/...", "key claims from this talk".

★ 1
zfifteen
zfifteen/skills-catalog

yeet

Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.

★ 1
zfifteen
zfifteen/skills-catalog

x-post-creator

Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, /x-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs/x-posts/[story-name]/.

★ 1
zfifteen
zfifteen/skills-catalog

x-api

Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X/x.com, reading threads and replies, creating lists, staging/publishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions /x-api or "search X".

★ 1