Przejdź do treści
Biblioteka skilli
DevOps i chmura · Automatyzacja

herdr-orca-release

/herdr-orca-release

Przygotowuje wydanie herdr-orca do Herdr Community i generuje plik CHANGELOG.md.

Repozytorium
herdr-orca ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
10.11.2026

Ocena i bezpieczeństwo

100/ 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ść35 / 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
0
Przestarzałość

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

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Przygotowuje wydanie herdr-orca do Herdr Community i generuje plik CHANGELOG.md.

Oryginalny opis (EN)

Use when cutting a release, publishing herdr-orca to Herdr Community, or generating CHANGELOG.md.

Jak działa

  1. Information Hierarchy & Roles
  2. Quick Reference
  3. Release Procedure
  4. Conventional Commits & Changelog Rules
  5. Invariants & Guardrails
Sekcje z nagłówków SKILL.md, w oryginale · 226 linii, 1 281 słów
Podgląd SKILL.md
---
name: herdr-orca-release
description: Use when cutting a release, publishing herdr-orca to Herdr Community, or generating CHANGELOG.md.
---

# Herdr Orca Release

Process, automation, and gates for cutting releases, generating changelogs, and publishing `herdr-orca` updates.

## Information Hierarchy & Roles

Distribution combines two independent mechanisms:
1. **Continuous Community Discovery**: `herdr.dev/layouts` crawls the `master` branch of public repositories carrying the `herdr-layout` topic within 60 minutes of push.
2. **SemVer Milestones & Archives**: Git tags (`vX.Y.Z`) and GitHub Releases provide stable checkpoints, upgrade guidance in `CHANGELOG.md`, and distribution archives (`.tar.gz`/`.zip`) without requiring downstream git clones.

---

## Quick Reference

| Task | Command | Completion Check |
|---|---|---|
| **Codebase Scan** | `/scan` | `.claude/pipeline/project-doc.md` updated, architecture reviewed |
| **Domain Modeling** | `/domain-modeling` | `GLOSSARY.md` sharpened, ADRs recorded in `docs/adr/` if needed |
| **Update Graph** | `graphify update .` | `./graphify-out/graph.json` refreshed (deterministic, AST offline) |
| **Syntax Check** | `for f in mods/*/main.js; do node --check "$f"; done` | Exit code 0 across all files |
| **Mod Check** | `for m in mods/*; do [ -d "$m" ] && herdr-app check "$m"; done` | All mods output `check passed` |
| **Dry Run** | `./scripts/release.sh --dry-run <version>` | Exit code 0, preview prints valid categories |
| **Cut Local Release** | `./scripts/release.sh <version>` | Tag `v<version>` created, `CHANGELOG.md` committed |
| **Publish Release** | `./scripts/release.sh <version> --push --github-release` | GitHub release live, assets attached |
| **Direct Changelog** | `uvx git-cliff --offline --tag v<version> -o CHANGELOG.md` | `CHANGELOG.md` updated |

---

## Release Procedure

Follow these five steps in exact order. Do not skip or reorder steps.

### Step 1: Pre-Flight Verification

Execute the pre-flight verification suite across code integrity, documentation drift, domain model precision, and code graph indexing:

```sh
# 1. Validate JavaScript syntax across all mod entrypoints
for f in mods/*/main.js; do
  node --check "$f"
done

# 2. Validate Herdr mod manifests and exports
for m in mods/*; do
  [ -d "$m" ] && herdr-app check "$m"
done

# 3. Update Knowledge Graph (graphify)
# Re-extract changed AST nodes into ./graphify-out/ (offline, code-only, no API key)
if command -v graphify >/dev/null 2>&1 && [ -d "graphify-out" ]; then
  graphify update .
fi

# 4. Check for uncommitted changes
git status --porcelain
```

#### Pre-Flight Skill Checks

Before finalizing the release commit, invoke and verify the following three disciplines:

1. **Codebase Scan (`/scan`)**:
   - Run a delta scan (or full scan on bootstrapping) to update `.claude/pipeline/project-doc.md`.
   - Update LOC counts, mod responsibilities, cross-cutting concerns, and citation verifications.
   - If architectural drift occurred, review and align `AGENTS.md` before proceeding.

2. **Domain Modeling (`/domain-modeling`)**:
   - Audit all terminology, UI boundaries, and concepts introduced or altered in this release cycle.
   - Sharpen `GLOSSARY.md`: confirm every concept has a canonical definition, explicit anti-terms ("Avoid: ..."), and zero implementation details.
   - Review architectural trade-offs: if a change was hard to reverse, surprising without context, and involved real trade-offs, ensure an ADR is recorded under `docs/adr/`.

3. **Code Graph Refresh (`graphify update .`)**:
   - Run `graphify update .` in the project root to ensure the local knowledge graph at `./graphify-out/graph.json` reflects the exact commit state.
   - Ensures subsequent agent queries (`graphify query`, `graphify path`, `graphify explain`) resolve all newly added symbols, dependencies, and calls without staleness.

4. **Commit Documentation & Alignment**:
   - Stage and commit all doc updates (`project-doc.md`, `GLOSSARY.md`, `AGENTS.md`, `docs/adr/`) under Conventional Commits (`docs(...)` or `docs: ...`) and push to `master`.

**Completion criterion:**
- `node --check` and `herdr-app check` exit 0 on all mod entrypoints.
- `.claude/pipeline/project-doc.md` reflects current LOC, architecture, and re-scanned files.
- `GLOSSARY.md` and `docs/adr/` accurately define all release domain terms and decisions.
- `graphify update .` exits 0 with `./graphify-out/graph.json` up to date.
- `git status --porcelain` is clean (or contains only dirty `CHANGELOG.md`/`cliff.toml` to be committed by the release runner).

---

### Step 2: Version Determination

Select the target SemVer version (`X.Y.Z`) based on commits since the latest git tag:
- **PATCH** (`0.1.0` → `0.1.1`): Bug fixes, layout tweaks, comment trims, docs.
- **MINOR** (`0.1.0` → `0.2.0`): New features, new mod additions, parity expansions, new non-breaking keybindings.
- **MAJOR** (`0.1.0` → `1.0.0`): Breaking changes to layout schema, mod removals, breaking key changes.

Inspect the automatic bump recommendation from commit history:
```sh
uvx git-cliff --bumped-version
```

Verify that the target tag does not already exist:
```sh
git rev-parse "v<version>" 2>/dev/null && echo "Tag exists!" || echo "Tag available"
```

**Completion criterion:** A unique SemVer string `X.Y.Z` is selected whose git tag `v<version>` does not exist in `git tag -l`.

---

### Step 3: Changelog Preview (Dry Run)

Run the release script in dry-run mode:

```sh
./scripts/release.sh --dry-run <version>
```

Inspect the generated changelog preview:
1. Verify commit entries fall into standard categories: `Features`, `Bug Fixes`, `Documentation`, `Styling`, `Refactoring`.
2. Verify commit scopes match affected components (e.g. `orca-spaces`, `orca-tabs`, `orca-files`).
3. Confirm unparsed multi-line bodies do not leak into bullet points.

**Completion criterion:** Dry-run exits 0, and changelog preview adheres to Keep a Changelog formatting without orphaned or unparsed text.

---

### Step 4: Execute Release & Tagging

Execute the release runner to update `CHANGELOG.md`, create the release commit, and tag the commit:

```sh
# Local commit and tag:
./scripts/release.sh <version>

# Or with immediate push and GitHub Release creation:
./scripts/release.sh <version> --push --github-release
```

**Completion criterion:**
- `CHANGELOG.md` contains the new `## [<version>] - YYYY-MM-DD` header.
- `git log -1 --oneline` shows commit `chore(release): v<version>`.
- `git tag -l "v<version>"` confirms the annotated tag exists locally.

---

### Step 5: Publishing & Upstream Verification

If `--push` and `--github-release` were omitted in Step 4, push and publish manually:

```sh
# Push branch and tags
git push origin master
git push origin "v<version>"

# Create GitHub Release
NOTES_FILE=$(mktemp)
uvx git-cliff --offline --tag "v<version>" --latest --strip header > "$NOTES_FILE"
gh release create "v<version>" --title "v<version>" --notes-file "$NOTES_FILE"
rm -f "$NOTES_FILE"
```

Verify published artifacts:
```sh
# 1. Verify GitHub Release and attached archives (.tar.gz and .zip)
gh release view "v<version>"

# 2. Verify Herdr Community topic
gh repo view mhenke/herdr-orca --json repositoryTopics
```

**Completion criterion:** `gh release view "v<version>"` shows the release with release notes and workflow-attached archives; repository topics include `herdr-layout`.

---

## Conventional Commits & Changelog Rules

`cliff.toml` parses Conventional Commits into structured sections:

```
<type>(<scope>): <short imperative description>
```

### Types & Changelog Mapping

| Commit Type | Scope Required? | Changelog Section |
|---|---|---|
| `feat` | Recommended | `Features` |
| `fix` | Recommended | `Bug Fixes` |
| `perf` | Recommended | `Performance` |
| `refactor` | Recommended | `Refactoring` |
| `style` | Optional | `Styling` |
| `docs` | Optional | `Documentation` |
| `chore` | `release` only | Excluded (except release notes) |

### Canonical Scopes

Use the affected mod or component folder:
- `orca-spaces` (sidebar projects, worktree tree, avatars)
- `orca-tabs` (tab strip, active indicators, titles, controls)
- `orca-files` (right-panel file tree, name filter, rg search)
- `orca-chrome` (window borders, titlebar left controls, footer)
- `orca-float` (floating workspace panel)
- `orca-landing` (welcome landing view)
- `orca-menu` (context menus, clipboard integration)
- `orca-nav` (sidebar search, navigation rows, projects header)
- `orca-pane` (terminal pane header, split controls)
- `orca-changes` (git staging, diffs, commits)
- `orca-status` (bottom status bar)
- `sync` (`scripts/sync.sh` installer)
- `layout` (`layouts/orca.json`)
- `theme` (`extras/themes/`)

---

## Invariants & Guardrails

1. **Package Shape Invariant (`herdr-t3` parity)**:
   - Permitted files: `layouts/`, `mods/`, `keys.json`, `extras/themes/`, `scripts/`, `README.md`, `RECIPE.md`, `CHANGELOG.md`, `preview.png`.
   - Never add `package.json`, `package-lock.json`, or `node_modules` to the repository. All tooling runs via `uvx`, `gh`, `node`, or `herdr-app`.
2. **Clean Working Tree**:
   - Never run release tagging with uncommitted code modifications.
3. **Automated Changelog Integrity**:
   - Maintain `CHANGELOG.md` exclusively through `git-cliff` (`cliff.toml`). Do not manually fabricate release sections or version links.
4. **Herdr Layout Topic**:
   - Ensure `mhenke/herdr-orca` carries the `herdr-layout` GitHub topic so `herdr.dev/layouts` crawler includes the layout.

Wersje

W bazie nie ma innych skilli o nazwie herdr-orca-release.

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

  • 86release
    Prowadzi listę kontrolną wydania moda herdr-containers: changelog, wersje, podgląd, przepisy, commity i publikację.
  • 100herdr
    Steruje Herdr i pomaga go skonfigurować, wyłącznie na wyraźną prośbę użytkownika.
  • 91herdr
    Obsługuje panele, karty, obszary robocze i agentów w istniejącej sesji Herdr na wyraźną prośbę.
  • 100herdr-orchestrate
    Orkiestruje panele, karty i przestrzenie Herdr: czyta ekrany, wysyła polecenia, odpowiada na pytania i ustawia sprawdzenia AFK.
  • 100release
    Prowadzi wydanie forka orca: zapisuje zmiany należące do forka, liczy wersję od upstreamu i pilnuje publikacji buildu.
  • 90herdr-machines
    Sprawdza SSH i Tailscale, zapisuje inne komputery w herdr i ustawia etykietę tego komputera, by agenci działali na kilku maszynach.

Uwagi i zgłoszenia

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