From 205e57aaeb64c87351d7b45a30c25d7097e32c68 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 27 Aug 2026 01:45:42 +0000 Subject: [PATCH] docs: give create_issue the GitHub-surface pointer its siblings have MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Every PyAutoBrain skill body that drives `gh` carries a pointer to skills/GITHUB_ACCESS.md, enforced by PyAutoBrain's test_gh_surface.py — but that test only walks PyAutoBrain/skills, so this Mind-side skill was the one `gh`-driving body without one. A remote run of $create-issue reached `gh issue create` with nothing telling it the MCP surface exists. Add the same blockquote, and split the `gh auth status` note so the MCP surface is told to use `issue_write` rather than to go and log in. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01NHQzyeUkEHqMmEZDo9zsNX --- skills/create_issue/SKILL.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/skills/create_issue/SKILL.md b/skills/create_issue/SKILL.md index d54284401..0cfc3214f 100755 --- a/skills/create_issue/SKILL.md +++ b/skills/create_issue/SKILL.md @@ -5,6 +5,13 @@ description: Convert a PyAutoMind prompt file into a GitHub issue and register i Turn a `PyAutoMind/` prompt into a tracked GitHub issue and register it. +> **Which GitHub surface are you on?** This skill spells its GitHub steps as +> `gh` commands, which name the *operation*, not necessarily the command: a +> Claude Code remote session has no `gh` and reaches GitHub through the +> `mcp__github__*` tools instead. Probe once (`command -v gh`) and translate +> via `PyAutoBrain/skills/GITHUB_ACCESS.md`. Do not install `gh` to close the +> gap — that page records why an installed one still fails. + A **PyAutoMind** primitive — it owns the mechanical **issue + registry write**: assemble the issue body, create the issue, register the task in `active.md`, move the prompt to `active/`, and push Mind state. The *reasoning* (classify repos, @@ -173,6 +180,8 @@ If step 0 already pushed, this carries only the active.md + `active/` changes. ## Notes - Always present the issue body for review before creating it. -- If `gh auth status` fails, tell the user to run `! gh auth login`. +- On the `gh` surface, if `gh auth status` fails, tell the user to run + `! gh auth login`. On the MCP surface there is nothing to log into — + create the issue with `issue_write` and carry on. - The detailed plan should be thorough enough that a fresh session could start from the issue alone.