Przejdź do treści
Biblioteka skilli
Programowanie · Automatyzacja

rollup

/rollup

Scala metadane ADR ze wszystkich repozytoriów produktu w jeden widok, uruchamiany w repozytorium domowym.

Repozytorium
docflow ↗
Licencja
MIT
Ostatnia zmiana repozytorium
22.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
2
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 22.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 sprawdzić przed instalacją
  • SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.

Co robi i kiedy

Scala metadane ADR ze wszystkich repozytoriów produktu w jeden widok, uruchamiany w repozytorium domowym.

Wyzwalacze z opisu

roll up the federationgenerate the product-wide ADR viewaggregate ADRs across the reposrefresh the roll-up
Oryginalny opis (EN)

Generate the federation roll-up catalogue for a multi-repo product — aggregate every member repo's ADR metadata into one derived, product-wide view, run from the home repo. Use when the user says "roll up the federation", "generate the product-wide ADR view", "aggregate ADRs across the repos", "refresh the roll-up", or invokes /rollup. NOT for regenerating a single repo's own INDEX (that happens in place during authoring/ship) and NOT for linting consistency (use the audit skill).

Jak działa

  1. Step 0 — Preconditions
  2. Step 1 — Enumerate members
  3. Step 2 — Collect each member's catalogue
  4. Step 3 — Handle unreachable members
  5. Step 4 — Write the roll-up
  6. Step 5 — Report
  7. Closing report
Sekcje z nagłówków SKILL.md, w oryginale · 91 linii, 665 słów
Podgląd SKILL.md
---
name: rollup
description: Generate the federation roll-up catalogue for a multi-repo product — aggregate every member repo's ADR metadata into one derived, product-wide view, run from the home repo. Use when the user says "roll up the federation", "generate the product-wide ADR view", "aggregate ADRs across the repos", "refresh the roll-up", or invokes /rollup. NOT for regenerating a single repo's own INDEX (that happens in place during authoring/ship) and NOT for linting consistency (use the audit skill).
---

# rollup

Aggregate the ADR catalogues of every repo in a multi-repo product into
one **derived, read-only** product-wide view. The roll-up is regenerated
from source, never hand-edited — treat it exactly like a repo's own
`INDEX.md`.

## Step 0 — Preconditions

1. This skill runs in the **index-holding repo** of a federation — the one
   that carries `federation-index.md` (its `Role` is `central` for
   topology A, `coordinator` for B, or `home` for C). Confirm
   `federation-index.md` and a `federation.md` whose `Role` is `central`,
   `home`, or `coordinator` exist. If they do not, stop: either this repo
   is standalone (nothing to roll up) or it is a plain member — point the
   user at the index-holding repo.
2. Read `federation.md` to learn the **identity scheme** (default
   repo-prefixed slug `<repo-id>/NNNN-slug`); roll-up rows use it.

## Step 1 — Enumerate members

Read `federation-index.md`. For each row, take the `Repo id` and the
`Pointer` (the path/URL of that member's checkout). The member index is
the **only** source of membership — do not auto-discover repos.

## Step 2 — Collect each member's catalogue

For every member whose checkout is **locally available** at its pointer:

- Read that member's `INDEX.md` (its authoritative local catalogue).
- For each ADR row, capture the number, title, status, date, and
  dependencies, and attach the **owning repo id** and the **federation
  identity** (the scheme from Step 0 applied to the local number).

A member's own `INDEX.md` stays authoritative for that member; this skill
only reads it.

For the **aggregate status** of a product-wide decision (one with owning
per-repo plan items across several members), also scan each member's
`plan/todo/` (pending) and `plan/done/` (shipped) for items naming that
decision's federation identity — that per-repo state feeds the aggregate
column in Step 4.

## Step 3 — Handle unreachable members

A member named in the index whose checkout is **not locally available** is
**not** dropped and **not** a failure. Record it in a clearly separated
"Not aggregated this run" list with its repo id and pointer, so the gap is
visible rather than silent.

## Step 4 — Write the roll-up

Write the aggregate to **`ROLLUP.md`** at the configured artefact root (the
same root as `INDEX.md`), so every re-run overwrites the same file:

- A header stating it is **generated — do not hand-edit**, with the run
  date and the set of members aggregated.
- One table across the whole product: federation identity, title, status,
  owning repo, date. Group or sort by owning repo for readability.
- For product-wide decisions, an **aggregate status** column **derived**
  from per-repo plan-item state: `Implemented` only when every owning
  per-repo plan item is in a member's `plan/done/`, otherwise `N of M
  repos` shipped. This column is derived — never written back into any ADR.
- The "Not aggregated this run" list from Step 3.

Do not alter any member's `INDEX.md` and do not write into any other repo.

## Step 5 — Report

Tell the user how many members were aggregated, how many were skipped as
unreachable (and which), and the total ADR count in the roll-up. Remind
them the file is derived: re-run this skill to refresh it rather than
editing it by hand.

Name catalogue coverage and unavailable members; partial coverage is not verification.

<!-- docflow:closing-report -->
## Closing report

End every run, including blocked, failed and stopped runs, with a section
headed exactly **Status at a glance**, containing these three labels:

- **This run:** only actions actually attempted and their outcomes; quote each verify gate's exact output and exit code, including timeouts or interruptions.
- **Overall:** implemented, partially verified, verified, blocked, failed or unknown. A passing sub-step is not an overall pass; incomplete or missing evidence never becomes success.
- **Yet to do:** every remaining action, unresolved finding, verification, cleanup or required input. Write None only when the whole task is verifiably complete; never omit work because a budget ended.

Routine progress messages need no block. Keep final results brief and
distinguish work prepared on a PR from work confirmed shipped.
<!-- /docflow:closing-report -->
Pliki w paczce (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · evolvehq/docflow90MIT
G1Joshi/Agent-Skills100MIT

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

  • 100ai-readiness-rollup
    Zbiera istniejące oceny gotowości AI z wielu repozytoriów w jeden raport portfelowy, porównując zespoły bez ponownego uruchamiania ocen.
  • 95audit
    Sprawdza repozytorium dokumentacji według jego konwencji: numeracji ADR, indeksu, pokrycia planów, linków i kolizji numerów między gałęziami.
  • 100adr-author
    Pisze i prowadzi rekordy decyzji architektonicznych w formacie MADR w repozytorium, zgodnie z jego konwencją.
  • 100module-health-rollup
    Zbiera wyniki pokrycia i testów do zdrowia modułów, przypisuje wiersze do modułów według mapy i zapisuje brakujące sygnały.
  • 100adr-tools
    Tworzy i zarządza rekordami decyzji architektonicznych za pomocą CLI adr-tools Nat Pryce'a: dodawanie, zastępowanie i łączenie ADR oraz generowanie spisu treści.
  • 100adr-review
    Recenzuje jeden lub kilka ADR (Architecture Decision Records) okiem osoby bez kontekstu, wskazuje problemy narracyjne i strukturalne, a następnie przepisuje dokumenty.

Uwagi i zgłoszenia

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