issue-sweep
/issue-sweep
Przegląda zaległe zgłoszenia GitHub od najstarszych w partiach i zamyka tylko te, które właściciel zatwierdzi w tabeli.
- Autor
- nativescript ↗
- Repozytorium
- nativescript ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 3
- Skrypty
- 2
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 2 skrypty w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/apply.mjs, scripts/fetch-batch.mjs
Co robi i kiedy
Przegląda zaległe zgłoszenia GitHub od najstarszych w partiach i zamyka tylko te, które właściciel zatwierdzi w tabeli.
Argumenty
/issue-sweep [batch-size]
Oryginalny opis (EN)
Sweep the GitHub issue backlog oldest-first in batches — fetch the next batch, classify each issue (already shipped, obsolete, duplicate, abandoned, won't do, still valid) with evidence from the codebase, present a review table, and close only what the maintainer approves. Use when asked to triage, clean up, or close stale/old/invalid issues.
Jak działa
- Phase 1: Fetch the next batch
- Phase 2: Classify each issue
- Phase 3: Present for review
- Phase 4: Apply
Podgląd SKILL.md
---
name: issue-sweep
description: Sweep the GitHub issue backlog oldest-first in batches — fetch the next batch, classify each issue (already shipped, obsolete, duplicate, abandoned, won't do, still valid) with evidence from the codebase, present a review table, and close only what the maintainer approves. Use when asked to triage, clean up, or close stale/old/invalid issues.
argument-hint: [batch-size]
---
# Issue Backlog Sweep
Closing an issue posts a public comment under the maintainer's account and notifies every subscriber. Nothing is closed, labeled, or commented until the maintainer has approved the table from Phase 3.
State lives in `~/.cache/nativescript-issue-sweep/`: `cursor` (the `createdAt` of the last fully swept issue), `log.jsonl` (every action taken), and the default batch files.
## Phase 1: Fetch the next batch
```bash
node .agent/skills/issue-sweep/scripts/fetch-batch.mjs --limit 25
```
Writes `batch.json` (raw) and `batch.md` (digest: truncated body, last 4 comments, labels, cross-referenced PRs/issues) to the state dir. `--after <ISO date>` overrides the cursor; `--out <path>` writes elsewhere. Read `batch.md`.
## Phase 2: Classify each issue
Assign exactly one bucket, and back it with evidence — a `file:line`, a commit/PR, or a quote from the thread. No evidence, no close.
| Bucket | Action | Evidence required |
| --- | --- | --- |
| **Shipped** | close `completed` | The feature/fix exists today: grep `packages/core` (read both platform files), `git log -S`, or a MERGED cross-ref PR. Name the API in the comment. |
| **Obsolete** | close `not planned` | Targets something gone: `tns-*` packages, JSC iOS runtime, Sidekick, NativeScript < 7 APIs, Bountysource/ideas-portal workflows, Android Support Library. |
| **Duplicate** | close `not planned` + `duplicateOf` | The canonical issue number; keep the one with more discussion/reactions open. |
| **Abandoned** | close `not planned` | Bug with no repro or `needs more info`, reporter silent > 1 year. |
| **Won't do in core** | close `not planned` | Out of scope for core, or covered by a plugin (name it), or a workaround is posted in the thread (link it). |
| **Still valid** | keep | Genuine gap, active PR, recent member engagement, or strong demand (many reactions / recent comments). Suggest label fixes. |
| **Your call** | flag | Mixed signals — present both readings; the maintainer decides. |
Judgment rules:
- Recent member activity (a maintainer commented in the last ~2 years, or an open PR references it) means **keep** unless that member said otherwise.
- For bugs, check whether the code path in the report still exists; if it was rewritten, lean toward Abandoned with a "please reopen with a repro on current `@nativescript/core`" invitation.
- Partial delivery: if the core ask shipped and leftovers have no demand, close `completed` and say what remains.
- Note related open issues found along the way (likely duplicates later in the backlog) so later batches can close them against a canonical one.
## Phase 3: Present for review
Write `decisions.json` (format in the header of `scripts/apply.mjs`; `batch` is a path relative to the decisions file) with a draft comment per close, then dry-run it:
```bash
node .agent/skills/issue-sweep/scripts/apply.mjs <decisions.json>
```
Show the maintainer a table — `#`, title, age, bucket, one-line evidence, proposed action — grouped by action, plus the "your call" items. Accept edits ("keep #59", "close #254 as dup of #27", "reword #944").
Closing comments: 2–4 sentences, warm and specific. Thank the reporter, state the evidence (the API/PR that shipped it, the plugin to use, or why it's out of scope), and invite a reopen or new issue against current `@nativescript/core` if it still matters. No boilerplate apologies, no "stale bot" tone.
## Phase 4: Apply
Only after explicit approval:
```bash
node .agent/skills/issue-sweep/scripts/apply.mjs <decisions.json> --execute
```
Before each action it re-checks the issue; anything closed or updated since the fetch is skipped for re-review. The cursor advances only when every decision applied, so skipped items come back in the next batch. Report the summary line and any FAIL/SKIP lines verbatim.
Pliki w paczce (3)
- SKILL.md 4 KB
- scripts/apply.mjs 5 KB
- scripts/fetch-batch.mjs 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · nativescript/nativescript | 100 | MIT |
| JacobPEvans/claude-code-plugins | 100 | Apache-2.0 |
| dryvist/claude-code-plugins | 100 | Apache-2.0 |
Migawka bazy z 13.11.2026 · wersja paczki 408ca0e0e044 (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
- 90sweep
Ocenia każde zgłoszenie z backlogu projektu osobnym subagentem, a zatwierdzone werdykty stosuje jako komentarz, przepisanie, zamknięcie lub anulowanie. - 100github-issue-triage
Przegląda, etykietuje i priorytetyzuje zgłoszenia GitHub, wykrywa duplikaty i nie zmienia nic bez wyraźnej prośby. - 90issue-tracker
Zakłada, aktualizuje i zamyka zgłoszenia GitHub w jednym epiku z podzadaniami zapisanymi natywnie w GitHubie. - 90issue-triage
Porządkuje zgłoszenia w repozytorium według drzewa decyzji: klasyfikuje, dodaje etykiety i wskazuje brakujące informacje. - 100issue-triage
Segreguje i kategoryzuje zgłoszenia GitHub, nadając etykiety priorytetu, podczas przeglądu otwartych zgłoszeń i regularnej obsługi backlogu. - 100issue-triage
Zarządza backlogiem zgłoszeń GitHub w trzech fazach (audyt, głęboka analiza, zweryfikowane akcje triage), w tym wykrywa duplikaty i nieaktualne zgłoszenia.