Przejdź do treści
Biblioteka skilli
Programowanie · Budowanie i kod

start-issue

/start-issue

Rozpoczyna pracę nad issue z GitHuba: pobiera kontekst, pisze testy, wdraża zmianę i przygotowuje pull request.

Repozytorium
gopher-ai ↗
Licencja
MIT
Ostatnia zmiana repozytorium
20.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 20.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Rozpoczyna pracę nad issue z GitHuba: pobiera kontekst, pisze testy, wdraża zmianę i przygotowuje pull request.

Wyzwalacze z opisu

start issue #N

Argumenty

/start-issue <issue-number> [--skip-coverage] [--coverage-threshold <n>] [--no-agents]
Oryginalny opis (EN)

Start implementation of a GitHub issue: fetch context, prepare worktree flow, implement with TDD, verify, and submit PR. Use for 'start issue #N', issue URLs, or requests to begin issue work. SKIP fully autonomous issue-to-merge requests; use complete-issue.

Jak działa

  1. Plugin Resource Resolution
  2. Setup and Durable State
  3. Workspace Before Planning
  4. Issue Classification
  5. Implementation Selection
  6. Verification and Submission Contract
  7. Completion Criteria
Sekcje z nagłówków SKILL.md, w oryginale · 114 linii, 602 słów
Podgląd SKILL.md
---
name: start-issue
description: "Start implementation of a GitHub issue: fetch context, prepare worktree flow, implement with TDD, verify, and submit PR. Use for 'start issue #N', issue URLs, or requests to begin issue work. SKIP fully autonomous issue-to-merge requests; use complete-issue."
argument-hint: "<issue-number> [--skip-coverage] [--coverage-threshold <n>] [--no-agents]"
disable-model-invocation: true
---

# Start Issue

## Plugin Resource Resolution

`<PLUGIN_ROOT>` is notation. Replace it with a concrete absolute plugin root before every resource read or command:

- **Codex:** Start from the directory containing the absolute selected `SKILL.md` path, then ascend two directories (`skills/<name>` -> plugin root).
- **Claude Code:** Bind it to the injected `${CLAUDE_PLUGIN_ROOT}` value.

Before decisions, planning, or delegation, read
`<PLUGIN_ROOT>/lib/driver-interaction.md`. Read
`<PLUGIN_ROOT>/lib/decision-gates.md` before resolving any workflow choice.
Bind `SKILL_ARGS` for `$go-workflow:start-issue` by reading
`<PLUGIN_ROOT>/lib/skill-arguments.md` with this compatibility payload:

<claude-skill-arguments>
$ARGUMENTS
</claude-skill-arguments>

## Setup and Durable State

Read `<PLUGIN_ROOT>/lib/start-issue/setup.md` completely. Execute **Empty
Arguments**, **Output Durability**, **Clear Stale Worktree State**, **Security
Validation & Flag Parsing**, and **Surface Dispatch Decision** in order.
A missing issue number is a missing-intent gate: request it and stop before loop
initialization or any completion claim.

After parsing, use only numeric `ISSUE_NUM`. Preserve `SKIP_COVERAGE`,
`COVERAGE_THRESHOLD` (default `60`), and `NO_AGENTS`.
`--skip-coverage` never waives coverage for changed source.

Read `<PLUGIN_ROOT>/lib/start-issue/loop-state.md` completely and execute
**Embedded Workflow Contract** and **Loop Initialization**. Standalone
start-issue owns its loop; embedded start-issue uses the caller file and child
path, never changes root promises or emits a child terminal marker.

Then execute **Context** from `setup.md` to fetch the issue, labels, comments,
default branch, checkout, and registered worktrees.

## Workspace Before Planning

Read `<PLUGIN_ROOT>/lib/start-issue/workspace.md` completely and execute it
before planning. Worktree selection is driver-resolvable; an existing isolated
worktree is reused without another worktree or branch-format gate. If creation
is selected, read `<PLUGIN_ROOT>/lib/start-issue/worktree-create.md` completely
and persist its absolute output before planning. Copying environment files
requires explicit consent.

Every repository command and file operation must explicitly target the resolved
`WORKTREE_PATH`. Never commit to the default branch.

## Issue Classification

Classify from labels, title, body, comments, and acceptance criteria. Check
labels first:

- Bug labels: `bug`, `fix`, `defect`, `error`, `regression`, `crash`.
- Feature labels: `enhancement`, `feature`, `feat`, `new`, `improvement`, `request`.

Only without clear labels, analyze title and body:

- Bug patterns: `fix`, `broken`, `error`, `fail`, `crash`, `doesn't work`, `issue with`, `problem`, `bug`, `regression`, `incorrect`.
- Feature patterns: `add`, `implement`, `create`, `new`, `support`, `enable`, `allow`, `introduce`, `enhance`.

If semantics remain ambiguous after all evidence, use the missing-intent gate
and stop before branch creation or implementation.

## Implementation Selection

For `NO_AGENTS=true`, or on Codex without the required native
`explorer`/`worker`/`default` delegation profiles, read
`<PLUGIN_ROOT>/lib/start-issue/manual-workflow.md` completely and execute its
single-session flow.

Otherwise read
`<PLUGIN_ROOT>/lib/start-issue/orchestrated-workflow.md` completely and execute
its full procedure with the active surface binding. Start-issue agent dispatch
is delegation, not another skill invocation.

Both flows preserve this order: explore/design, TDD red before implementation,
minimal green, build/test/lint, coverage, security review, scoped commit/push,
non-draft PR creation, and current-head CI. Bugs also perform duplicate
detection. Features resolve approach from requirements, repository patterns,
reversibility, and risk.

## Verification and Submission Contract

Before commit, push, or PR creation, fresh evidence must show the project build
and tests pass, configured lint passes (when installed), coverage is verified
for changed source, and security review is complete. Read
`<PLUGIN_ROOT>/lib/coverage/coverage-verification.md` for coverage.

After publishing, read
`<PLUGIN_ROOT>/lib/start-issue/ci-monitoring.md` completely and require
successful REST monitoring for the exact pushed head. Prior-head or absent
checks are not passing evidence.

If any supporting file produces an incomplete result, execute **Workflow Result
Contract** from `loop-state.md` and stop. Embedded runs persist structured
incomplete state without a marker; standalone runs persist then emit only
`<done>INCOMPLETE</done>`.

## Completion Criteria

Complete only when implementation addresses the issue, tests and build pass,
coverage is verified or source-free, configured lint passes, changes are
committed and pushed, a non-draft PR exists, and exact-head CI is green.

Execute **Successful Result** from `loop-state.md` only after all criteria
hold. Embedded success returns structured state without a marker; standalone
success emits `<done>COMPLETE</done>`. After 15 unsuccessful iterations,
persist incomplete evidence and stop.
Pliki w paczce (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · gopherguides/gopher-ai90MIT
hmislk/hmis100GPL-3.0
sejas/ai-code-skills90MIT

Migawka bazy z 28.10.2026 · wersja paczki 1dae499976d0 (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

  • 90complete-issue
    Prowadzi zgłoszenie GitHub od implementacji do scalonego pull requesta, bez przerw, gdy zlecono pełną automatyzację.
  • 90start-work
    Rozpoczyna lub wznawia pracę nad zadaniem Jira: pobiera kontekst, tworzy gałąź i aktualizuje status.
  • 100start
    Rozpoczyna pracę nad zgłoszeniem Linear: sprawdza blokery, przypisuje zadanie, przygotowuje gałąź i planuje implementację.
  • 84implement
    Implementuje zgłoszenie z GitHuba zgodnie z planem i tworzy pull request z gotową zmianą.
  • 100work
    Rozpoczyna pracę nad zgłoszeniem lub pull requestem w izolowanym worktree, na podstawie linku albo opisu.
  • 100pick-up-issue
    Pomaga przejąć zgłoszenie GitHub przed rozpoczęciem pracy: wybór zgłoszenia, zajęcie go i start pracy nad nim.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.