Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

izumo

/izumo

Prowadzi zadania obejmujące wiele repozytoriów narzędziem izumo: jeden folder na zadanie i jedno worktree Gita na repozytorium.

Repozytorium
izumo ↗
Licencja
MIT
Ostatnia zmiana repozytorium
04.11.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
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 04.11.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

Prowadzi zadania obejmujące wiele repozytoriów narzędziem izumo: jeden folder na zadanie i jedno worktree Gita na repozytorium.

Wyzwalacze z opisu

s app running (this also needs repo Chow are my tasks?clean up what shippedget it running so I can check it
Oryginalny opis (EN)

Work on multi-repo tasks with the izumo CLI, one folder per task with one git worktree per repo. Use when the current directory, or a parent, has a .izumo file and the user starts, resumes, extends, checks or finishes a piece of work, asks about pull requests, CI, what shipped or what is running, or wants a task's app running ("start task X in A and B", "this also needs repo C", "how are my tasks?", "clean up what shipped", "get it running so I can check it").

Jak działa

  1. Rules
Sekcje z nagłówków SKILL.md, w oryginale · 60 linii, 713 słów
Podgląd SKILL.md
---
name: izumo
description: Work on multi-repo tasks with the izumo CLI, one folder per task with one git worktree per repo. Use when the current directory, or a parent, has a .izumo file and the user starts, resumes, extends, checks or finishes a piece of work, asks about pull requests, CI, what shipped or what is running, or wants a task's app running ("start task X in A and B", "this also needs repo C", "how are my tasks?", "clean up what shipped", "get it running so I can check it").
---

# izumo

Installed as the Claude Code plugin, `izumo` is already on your Bash PATH. Otherwise it
must be on PATH; if it is missing, point the user to https://github.com/migueww/izumo#install.

## Rules

- **Never edit the source clones** at the root. All work happens in `tasks/<task>/<repo>`.
- **A repo the task only reads** (the back end whose payload the front needs, another
  service's contract): `izumo add <repo> --ref` from inside the task folder. It lands in
  the task, detached on the task's base, without a branch; never edit it. Run `izumo pull
  <repo>` before reading it again later, so you don't read stale code. If the task turns
  out to change it, `izumo add <repo>` (no `--ref`) turns it into a worktree on the task's
  branch. Outside a task, read the root clone after `izumo pull <repo>`; if that says the
  clone is on some other branch, tell the user what you read may not be the base branch.
- **Starting work:** `izumo new <task> <repos...>`, with `--branch` when the user or the
  team convention names the branch. Write the user's request into the first section of
  `TASK.md` (the goal; the root's template may name its sections in another language)
  right away.
- **Existing worktree made by hand?** `izumo adopt <path> --task <task>` moves it into a
  task (creating the task if needed) instead of starting over.
- **Scope grows:** `izumo add <repo>` from inside the task folder, then add one line under
  Decisions saying why the repo joined.
- **Scope shrinks:** `izumo drop <repo>` from inside the task folder, never `git worktree
  remove` or hand edits to the workspace file. Add one line under Decisions saying why the
  repo left. A repo that belongs to another task moves with `izumo adopt
  tasks/<from>/<repo> --task <to>`.
- **Renaming a task or changing its base:** `izumo mv <task> <new-name>`, `izumo base
  <branch>`. Never rename task folders or edit `.task` by hand: git tracks the worktree
  paths.
- **TASK.md holds only what git can't tell:** goal, status / next step, decisions, open
  items. Never list repos, branches or PRs there; `izumo ls <task> --json` has them.
- **Before ending a session**, update "Status / next step" with the next thing a person
  does ("test a handover in hml", "decide the template item"), never PR or merge state:
  that changes after your session ends, and `izumo ls` always has it right.
- **Same command in every repo** (tests, lint, `git status`): `izumo run -- <command>` from
  inside the task folder, instead of a loop. It fails if any repo failed and names them.
- **State:** `izumo ls <task> --json`. Add `--fetch` when freshness matters (after a
  merge or promotion). The `agent` field comes from this plugin's hooks; don't write
  `.agent` yourself. `conflict: true` means the open PR can't merge into its base. A repo
  in `prod` often has an empty `pr`: once its commits are in prod, izumo doesn't ask
  GitHub, so don't report its PR as missing.
- **Removing:** only when the user asks. Name the task: `izumo done <task> --dry-run` (or
  `rm <task> --dry-run`) first, show the result, then run it for real. Bare `izumo done`
  sweeps every task; use it only when the user asks to clean up everything that shipped. Never work around a refusal
  by committing, pushing or deleting files on your own; report what blocked it. Use `rm
  --discard` only when the user said to throw that work away; run it with `--dry-run`
  first and show what would be lost. A
  removal that stopped halfway finishes by running the same command again.
- **Dev servers:** before starting one (`pnpm dev`, `npm start`...), check `izumo ls <task>
  --json`: if the repo already has one in `servers`, use its port instead of starting
  another. When you no longer need a server you started, `izumo stop <repo>` from inside
  the task folder; don't stop servers you didn't start unless the user asks. When a
  removal's dry run says it would also stop servers (`and stop node on :3000 ...`), ask the
  user before the real run, then pass `--stop`, or `--no-stop` if they want them left
  running. Without either flag the removal refuses, since you have no terminal.
- `TASK.md` is local. When opening a PR, carry the decisions reviewers need into its
  description.

Wersje

W bazie nie ma innych skilli o nazwie izumo.

Migawka bazy z 13.11.2026 · wersja paczki ff22e2be9112 (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

  • 100task-onboarding
    Podłącza repozytorium git do zadań worktree tt z unikalnymi portami na zadanie i szablonami środowiska, wymagając CLI tt.
  • 100track-cross-repo-task
    Tworzy jedno zadanie obejmujące kilka repozytoriów, z jednym wynikiem i zgłoszeniem przypisanym do każdego repozytorium.
  • 100worktree-new
    Tworzy worktree zadania poleceniem aidrian i uruchamia bootstrap projektu.
  • 100worktree
    Obsługuje worktree gita w repozytorium: listowanie, tworzenie i przełączanie, usuwanie oraz konfigurację przez git-wt.
  • 100tasks
    Prowadzi zadania jako pliki Markdown w katalogu .tasks każdego repozytorium, z zależnościami między repozytoriami i przeglądem projektów.
  • 100worktree
    Tworzy worktree gita dla nowej gałęzi funkcji i przygotowuje w nim pliki oraz zależności.

Uwagi i zgłoszenia

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