Skip to content

docs: give create_issue the GitHub-surface pointer its siblings have #344

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jammy2211 merged 1 commit into from
Aug 27, 2026
Merged

docs: give create_issue the GitHub-surface pointer its siblings have #344

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion skills/create_issue/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down Expand Up @@ -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.
Loading