Github Issues logo

Github Issues

Community
dannote
github-issues

Use gh CLI to view, triage, fix, link, create, or close GitHub Issues.

Overview

Publisherdannote
Repositorydot-pi
Skill namegithub-issues
Stars
57
Forks
4
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dannote on GitHub. Read the source before you install it.

Installation

Install the Github Issues AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/dannote/dot-pi/tree/master/skills/github-issues
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dannote/dot-pi.git /tmp/dot-pi
mkdir -p .claude/skills
cp -r /tmp/dot-pi/skills/github-issues .claude/skills/github-issues
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Github Issues in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Github Issues on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Github Issues is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

GitHub Issues Workflow

Markdown bodies: never inline multiline text

Never pass multiline Markdown through --body "...". Shell quoting can leak literal \n into GitHub.

Always write Markdown to a temp file and use --body-file:

bash
cat > /tmp/body.md <<'EOF'
## Summary

- ...

## Tests

- `...`
EOF

gh pr create --body-file /tmp/body.md
# or
gh pr edit <number> --body-file /tmp/body.md
# or
gh issue create --body-file /tmp/body.md

Review handoff

For PR inspection, use the pr-review skill. This skill handles GitHub issue and PR mechanics such as reading templates, using --body-file for multiline Markdown, and checking existing comments before closing or posting.

View issue

bash
gh issue view <number>

Create issue safely

For non-trivial bodies, always write the draft to a temp file first. Do not inline long Markdown with shell quoting.

bash
cat > /tmp/issue.md <<'EOF'
### What happened?

...
EOF

gh issue create --repo OWNER/REPO --title "Short title" --body-file /tmp/issue.md

Before creating issues in someone else's repo, check templates/contributing docs and keep the report concise.

bash
gh api repos/OWNER/REPO/contents/.github/ISSUE_TEMPLATE --jq '.[].name'
gh api repos/OWNER/REPO/contents/CONTRIBUTING.md --jq .content | base64 --decode

If gh issue create prompts for confirmation, review the preview carefully before accepting.

Link issues in commits, changelogs, releases

  • Commits: fix: description (#1) or fix: description (fixes #1) — auto-closes on merge to default branch
  • Changelog: ([#1](https://github.com/owner/repo/issues/1))
  • Release notes: fixes #1 — does NOT auto-close, must close manually

Public replies

Use the maintainer-reply skill before drafting or posting issue and PR replies. Read the conversation first; do not apply a generic thank-you or mention a fix version when it is unknown or irrelevant.

Close with comment

When closing with a reply, mention the fix version when known and thank the reporter when appropriate to the conversation:

bash
gh issue close <number> --comment "Fixed in v1.2.3. Thanks for the report!"

Test fixes before closing

For npm packages, simulate fresh install:

bash
npm pack --pack-destination /tmp/
cd /tmp && mkdir test && cd test
echo '{"name":"test"}' > package.json
bun add /tmp/package-name-1.0.0.tgz
./node_modules/.bin/command --help

Frequently asked questions

What does the Github Issues AI skill do?

Use gh CLI to view, triage, fix, link, create, or close GitHub Issues.

Why use Github Issues on TypingMind?

Because you install it once and use it with any model. Github Issues is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Github Issues in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dannote/dot-pi/tree/master/skills/github-issues. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Github Issues?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Github Issues?

As many as you like. As long as a model supports skills, you can use Github Issues with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Github Issues AI skill free?

Yes. It is published on GitHub by dannote under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇