read-issues
/read-issues
Wyświetla zgłoszenia z GitHub, pozwala wybrać jedno i pobiera jego treść wraz z obrazkami, żeby agent mógł nad nim pracować.
- Autor
- thefrederiksen ↗
- Repozytorium
- devthrottle ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 27.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 3
Brak sygnałów. Repozytorium zmienione 27.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wyświetla zgłoszenia z GitHub, pozwala wybrać jedno i pobiera jego treść wraz z obrazkami, żeby agent mógł nad nim pracować.
Argumenty
/read-issues [optional: issue number, label filter, or search query]
Oryginalny opis (EN)
List GitHub issues, let the user pick one, and download all content including images so an agent can work on it. Use this when the user wants to browse, review, or select issues to work on.
Jak działa
- Input: $ARGUMENTS
- Instructions
- Important Notes
Podgląd SKILL.md
--- name: read-issues description: List GitHub issues, let the user pick one, and download all content including images so an agent can work on it. Use this when the user wants to browse, review, or select issues to work on. disable-model-invocation: true argument-hint: "[optional: issue number, label filter, or search query]" --- # Read GitHub Issues Browse, filter, and select GitHub issues, then download all content and images so an agent can fully understand and work on the selected issue. ## Input: $ARGUMENTS ## Instructions ### Step 1: List Issues If a specific issue number is provided in `$ARGUMENTS`, skip to Step 2. If a search query or label filter is provided, use it: ```bash # By label gh issue list --label "bug" --state open # By search gh issue list --search "QUERY" --state open # All open issues gh issue list --state open --limit 30 ``` If no filter is provided, list all open issues: ```bash gh issue list --state open --limit 30 ``` Display the issues in a clear format showing: - Issue number - Title - Labels - Assignee - Created date ### Step 2: Select an Issue - If `$ARGUMENTS` contains a specific issue number, use that directly - Otherwise, use AskUserQuestion to let the user pick which issue to work on - Present the top issues as options with their titles ### Step 3: Download Full Issue Content Once an issue is selected, fetch everything: ```bash # Get full issue details including body gh issue view ISSUE_NUMBER # Get all comments gh issue view ISSUE_NUMBER --comments # Get issue metadata as JSON for structured parsing gh issue view ISSUE_NUMBER --json title,body,labels,assignees,comments,state,milestone,createdAt,updatedAt,author ``` ### Step 4: Extract and Download Images 1. Parse the issue body and all comments for image URLs 2. Look for patterns like: - `` — Markdown images - `https://github.com/user-attachments/...` — GitHub uploaded images - `https://user-images.githubusercontent.com/...` — Legacy GitHub images 3. For each image found: - Download it to a temporary location using `curl` or `Invoke-WebRequest` - Save to a temp directory like `$env:TEMP/gh-issues/ISSUE_NUMBER/` - Read the image using the Read tool so Claude can see it 4. If no images are found, note that and continue ### Step 5: Present Complete Issue Context Provide a comprehensive summary including: ```markdown ## Issue #NUMBER: TITLE **State:** open/closed **Labels:** label1, label2 **Assignee:** @username **Created:** date **Author:** @username ### Description [Full issue body] ### Images [Display all downloaded images] ### Comments (N total) [All comments with authors and dates] ### Key Requirements - [Extracted actionable items from the description] - [Any acceptance criteria mentioned] ### Related Files (if mentioned) - [Any file paths or code references from the issue] ``` ### Step 6: Offer Next Steps After presenting the issue, ask the user: - Would you like to implement this issue? (suggest using `/developer-agent NUMBER`, or `/implementation-loop NUMBER` to drive it through Dev+QA to merged) - Would you like to assign it to yourself? - Would you like to add a comment? ## Important Notes - Always use `gh` CLI for all GitHub operations - Download images so Claude can actually see and understand visual bug reports - Parse both the issue body AND all comments for complete context - If the repo has many issues, default to showing only open ones
Wersje
W bazie nie ma innych skilli o nazwie read-issues.
Migawka bazy z 13.11.2026 · wersja paczki b0deb650f235 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100issue-run
Wyświetla ostatnie otwarte zgłoszenia GitHub lub Linear, pozwala wybrać jedno i uruchamia na nim autopilota przez skill run. - 100pick-up-issue
Pomaga przejąć zgłoszenie GitHub przed rozpoczęciem pracy: wybór zgłoszenia, zajęcie go i start pracy nad nim. - 100qa-to-issues
Prowadzi interaktywną sesję QA, w której użytkownik zgłasza błędy rozmownie, a agent zakłada zgłoszenia w GitHub. - 100fetch-issues
Wyświetla otwarte zgłoszenia z trackera zapisanego w docs/agents/issue-tracker.md, np. GitHub, Jira lub lokalny markdown, wyłącznie do odczytu. - 100github
Pracuje z kodem, zgłoszeniami, pull requestami i komentarzami na GitHubie: klonuje, wypycha, czyta pliki, tworzy zgłoszenia i PR. - 87github-issues
Czyta i obsługuje zgłoszenia GitHub przez gh CLI, gdy użytkownik poda link do issue albo poprosi o pracę nad zgłoszeniem.