Repository navigation
docs: give create_issue the GitHub-surface pointer its siblings have - #344
Merged
Merged
Conversation
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 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NHQzyeUkEHqMmEZDo9zsNX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Every PyAutoBrain skill body that drives
ghcarries a pointer toskills/GITHUB_ACCESS.md, enforced by PyAutoBrain'stest_gh_surface.py. That guard only walkedPyAutoBrain/skills, so this Mind-side skill was the onegh-driving body without a pointer — invisible to the check. A remote run of$create-issuereachedgh issue createwith nothing telling it the MCP surface exists.What changed
skills/create_issue/SKILL.md:PyAutoBrain/skills/GITHUB_ACCESS.mdas a bare workspace path (a../../../link across repos would be noise).gh auth statusnote. It previously said, unconditionally, to tell the user to run! gh auth login— actively wrong advice on the MCP surface, where there is nothing to log into. It now sends that run toissue_writeinstead.Merge order: this one goes first
Correcting an earlier claim in this description that the two PRs were independent — they are not.
The companion PR PyAutoLabs/PyAutoBrain#300 widens
test_gh_surface.pyto walk this repo's skill root. Brain'stests.ymlchecks PyAutoMind out pinned to main, by design — that gate tests Brain against the current organism identity. So the widened guard asserts against this repo's livemain, and Brain#300's CI is red until this PR merges. Merge this first, then Brain#300 goes green on a re-run.Testing
python3 -m pytest -q -n auto— 240 passed. Spawn Drift green on this PR.