AGENT SKILL

issue

Create a GitHub issue from conversation context; auto-labels bug-agentmade

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

01 前言 Front Matter

name
issue
description
Create a GitHub issue from conversation context; auto-labels bug-agentmade
allowed-tools
Bash(bash *create_issue.sh*), Bash(open *), Bash(xdg-open *)
argument-hint
[optional user summary]

02 资源文件 1

03 SKILL.md 正文

Permission note: This skill runs Bash to create issues. You may be prompted to allow Bash execution. To skip future prompts, add to .claude/settings.json: "Bash(bash *create_issue.sh*)"

Phase 1 — Populate fields (Claude):

Redact before writing any field: replace tokens/keys/passwords → [TOKEN], emails → [EMAIL], IPs → [IP], absolute paths → [PATH], UUIDs → [UUID]. No repo-specific names, env var values, or internal hostnames.

  1. Capture $ARGUMENTS as user_summary (omit field if empty)
  2. Scan conversation for most recent failure: plugin name, skill name, command run, error category
  3. Construct:
    • TITLE: [issue] <skill>: <one-line error>
    • BODY (one line each):
      plugin: <name>
      skill: <name>
      user_summary: <$ARGUMENTS>
      situation: <one-line: what was attempted>
      complication: <one-line: error or failure — no raw values>
      error_type: <category: validation | auth | network | parse | other>
      steps_to_reproduce: <concise numbered steps, generic — no internal specifics>
      
    • Do not add version fields yourself — create_issue.sh appends plugin_version: and skillhub_version: automatically, read from the actual installed state (not guessed), so a report against an already-fixed version is visible on sight.

Redaction audit (do this before Phase 2): Re-read every field. Replace any specific project, folder, repo, or org name with [PROJECT], path segments with basepath/subpath, org names with [ORG]. When in doubt, redact it.

Script path: The harness injects Base directory for this skill: <path> at the very top of these instructions. That full path is BASE_DIR — it already ends in .../skills/issue. Do not trim or modify it.

Phase 2 — Create issue (Bash):

Pass TITLE and BODY via env vars (safe for quotes/special chars):

ISSUE_TITLE="<TITLE>" ISSUE_TEXT="<BODY content>" bash "<BASE_DIR>/create_issue.sh"

(substitute the actual BASE_DIR path)

If exit code is 2 (FORMAT ERROR):

  • Read the error output — each - body missing required field: '<field>:' line names a missing field
  • Fix TITLE and/or BODY to satisfy all listed fields
  • Retry Phase 2 immediately with the corrected values — max 2 retries
  • If still exit 2 after 2 retries: output the raw error and STOP — do not proceed to URL fallback

If exit code is 0: output Issue: <url> and STOP. If exit code is 1: output the error and STOP.

If the script output contains "Could not create issue automatically":

  • Extract the URL from the output
  • If the script did not report "✓ Opened in browser", run: open "<URL>" 2>/dev/null || xdg-open "<URL>" 2>/dev/null via Bash
  • If that also fails, the script prints a echo <base64> | base64 -d | xargs open command — surface that command to the user as plain assistant text instead of the raw URL (long URLs get split across lines by terminal rendering and become unpasteable; the base64 one-liner avoids that)
  • Otherwise (open succeeded, or as a last resort), repeat the URL as plain assistant text (not inside a tool block) so the user can see and copy it

04 同仓库更多 Skills