GitHub Issues
Use this skill to inspect and summarize GitHub issues for the current repository.
Workflow
Detect the repository:
gh repo view --json nameWithOwner -q '.nameWithOwner'
If this fails, do not infer that the directory is not connected to GitHub. Check
git remote get-url origin (or the relevant remote), resolve its owner/repo, and
retry the read-only lookup. Retry gh api user --jq .login to distinguish an
authentication/API problem from a missing or unusable remote; report the exact
diagnosis before stopping.
Run the narrowest query that matches the request:
gh issue list --repo <owner/repo> --state open
gh issue view <number> --repo <owner/repo>
gh issue list --repo <owner/repo> --state open --label "<label>"
gh issue list --repo <owner/repo> --state closed --limit 10
gh issue list --repo <owner/repo> --state open --search "<query>"
Present results compactly.
- For issue lists, group by label and show
#number - title.
- For one issue, show title, status, labels, body summary, comments/actions, and any referenced files.
- Mention Grimnir Roadmap board relevance when visible.
Prepare or publish a routed issue when requested.
- Resolve the owning repository and search it for likely duplicates before drafting.
- Prepare a title, verified labels only, and a temporary body file containing the
problem, evidence, proposed fix, source, and owning-repository attribution.
For cross-repo Grimnir work, add
from:<sender> when the target uses sender
labels and include Filed by: <sender> in the body.
- Preview the exact owner/repo, title, labels, body, and any board target. Use
gh issue create --repo <owner/repo> --title ... --body-file <file> only after
explicit user direction to publish. Preparation alone does not publish.
- Only the owning Grimnir session may add an item to the Grimnir Roadmap board,
and only with explicit authorization for that board mutation. Report board
relevance without adding it otherwise.
Offer a concrete next step only when useful: inspect, implement, close with a comment, or create a missing issue. Creating, commenting, closing, or adding to a board requires explicit user direction.
Cross-Repo Rule
If a fix belongs in another Magnus-owned repo, file a GitHub issue in the owning repo instead of editing that repo directly. Add from:<sender> when the target repo uses sender labels, include Filed by: <sender> in the issue body, and leave board placement to the owning Grimnir session under explicit owner authorization. Follow the preparation and publication boundary above.
Rules
- Always pass
--repo; do not rely on working-directory inference.
- Keep list views scannable.
- Do not close or merge anything without explicit user direction.
- Use issue body files for complex issue creation instead of shell-inlined markdown.
1---2name: issues-23description: Inspect current-repository GitHub issues or prepare a specifically requested routed issue. Use when the user asks to list, view, filter, search, or create an issue.4---56# GitHub Issues78Use this skill to inspect and summarize GitHub issues for the current repository.910## Workflow11121. Detect the repository:13 ```bash14 gh repo view --json nameWithOwner -q '.nameWithOwner'15 ```16 If this fails, do not infer that the directory is not connected to GitHub. Check17 `git remote get-url origin` (or the relevant remote), resolve its owner/repo, and18 retry the read-only lookup. Retry `gh api user --jq .login` to distinguish an19 authentication/API problem from a missing or unusable remote; report the exact20 diagnosis before stopping.21222. Run the narrowest query that matches the request:23 ```bash24 gh issue list --repo <owner/repo> --state open25 gh issue view <number> --repo <owner/repo>26 gh issue list --repo <owner/repo> --state open --label "<label>"27 gh issue list --repo <owner/repo> --state closed --limit 1028 gh issue list --repo <owner/repo> --state open --search "<query>"29 ```30313. Present results compactly.32 - For issue lists, group by label and show `#number - title`.33 - For one issue, show title, status, labels, body summary, comments/actions, and any referenced files.34 - Mention Grimnir Roadmap board relevance when visible.35364. Prepare or publish a routed issue when requested.37 - Resolve the owning repository and search it for likely duplicates before drafting.38 - Prepare a title, verified labels only, and a temporary body file containing the39 problem, evidence, proposed fix, source, and owning-repository attribution.40 For cross-repo Grimnir work, add `from:<sender>` when the target uses sender41 labels and include `Filed by: <sender>` in the body.42 - Preview the exact owner/repo, title, labels, body, and any board target. Use43 `gh issue create --repo <owner/repo> --title ... --body-file <file>` only after44 explicit user direction to publish. Preparation alone does not publish.45 - Only the owning Grimnir session may add an item to the Grimnir Roadmap board,46 and only with explicit authorization for that board mutation. Report board47 relevance without adding it otherwise.48495. Offer a concrete next step only when useful: inspect, implement, close with a comment, or create a missing issue. Creating, commenting, closing, or adding to a board requires explicit user direction.5051## Cross-Repo Rule5253If a fix belongs in another Magnus-owned repo, file a GitHub issue in the owning repo instead of editing that repo directly. Add `from:<sender>` when the target repo uses sender labels, include `Filed by: <sender>` in the issue body, and leave board placement to the owning Grimnir session under explicit owner authorization. Follow the preparation and publication boundary above.5455## Rules5657- Always pass `--repo`; do not rely on working-directory inference.58- Keep list views scannable.59- Do not close or merge anything without explicit user direction.60- Use issue body files for complex issue creation instead of shell-inlined markdown.
Magnus-Gille