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

kickstart-release

/kickstart-release

Przeprowadza listę kontrolną wydania: testy, skany, migracje z wycofaniem, wersję, monitoring i publikację na produkcji.

Licencja
MIT
Ostatnia zmiana repozytorium
06.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 06.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

Przeprowadza listę kontrolną wydania: testy, skany, migracje z wycofaniem, wersję, monitoring i publikację na produkcji.

Wyzwalacze z opisu

ship it\release\deploy to production\cut a version\are we ready to launch\
Oryginalny opis (EN)

Pre-release checklist and release execution for a kickstarted project: tests green, vulnerability and secret scans clean, migrations reviewed with rollback, changelog and version bump, monitoring and alerts confirmed, compliance evidence updated, then tag and deploy. Blocks on failures in enforced mode, warns in advised mode. Use when the user says \"ship it\", \"release\", \"deploy to production\", \"cut a version\", \"are we ready to launch\", or before any production deployment.

Jak działa

  1. Inputs
  2. Step 1: Pre-flight (read-only, fast)
  3. Step 2: Version and changelog
  4. Step 3: Build and verify artefact
  5. Step 4: Deploy
  6. Step 5: Post-release
  7. Step 6: Report
  8. Rules
Sekcje z nagłówków SKILL.md, w oryginale · 72 linii, 787 słów
Podgląd SKILL.md
---
name: kickstart-release
description: "Pre-release checklist and release execution for a kickstarted project: tests green, vulnerability and secret scans clean, migrations reviewed with rollback, changelog and version bump, monitoring and alerts confirmed, compliance evidence updated, then tag and deploy. Blocks on failures in enforced mode, warns in advised mode. Use when the user says \"ship it\", \"release\", \"deploy to production\", \"cut a version\", \"are we ready to launch\", or before any production deployment."
---

# kickstart-release

A release is a checklist that either passes or explains exactly why not. Run it the same way every time.

## Inputs

`.kickstart/project.md` (commands, enforcement, scale, hosting), `.kickstart/compliance.md`, `CHANGELOG.md`, git state.

## Step 1: Pre-flight (read-only, fast)

Run and report each as pass / warn / fail:

| # | Check | Command or source | Fail means |
|---|---|---|---|
| 1 | Clean working tree, on the release branch | `git status`, `git branch` | uncommitted changes |
| 2 | Lint and typecheck | `project.md` commands | any error |
| 3 | Tests | `project.md` test command | any failure |
| 4 | Secret scan (full history on first release, diff since last tag after) | `kickstart-guardrails` secret-scan.sh | any finding |
| 5 | Dependency vulnerabilities | ecosystem audit or osv-scanner | critical or high |
| 6 | Audit score | `kickstart-audit` script | below 70 (`pet`) or 85 (`scale`), or dropped since last release |
| 7 | Migrations | list pending migrations | destructive change without expand/contract note |
| 8 | Changelog | `CHANGELOG.md` Unreleased section | empty |
| 9 | Env parity | compare `.env.example` keys with production config (ask the user or check platform CLI) | missing variable in production |
| 10 | Monitoring | error tracker DSN set in prod, health endpoint reachable, uptime check exists | any missing (`scale`); warn for `pet` |
| 11 | Compliance | `.kickstart/compliance.md` rows touched since last release have status and evidence; framework records re-verified within 60 days via `kickstart-compliance` (its `freshness.py check`) so the release is judged against current deadlines and obligations | stale rows, or a framework changed and the checklist was not updated |
| 12 | Rollback plan | `docs/runbook.md` rollback section present and matches the hosting platform | missing |
| 13 | Features converged | every `specs/NNN-*/` changed since the last tag has `status: done` and its last converge run reported Converged | a shipped feature with open or appended tasks |
| 14 | Bugs verified and constitution respected | every `.kickstart/bugs/*/verification.md` changed since the last tag says `verified`; no unjustified constitution exception in the shipped plans | a `partial` or `failed` bug fix, or an exception missing from Complexity Tracking |

In `enforced` mode, any `fail` stops here. In `advised` mode, list the fails, say "ADVISED: would have blocked", and ask for an explicit "proceed anyway".

Show the result as a 14-line table, then a one-line verdict.

## Step 2: Version and changelog

- Determine the next version from Conventional Commits since the last tag: `feat` → minor, `fix` → patch, `!` or `BREAKING CHANGE` → major. Pre-1.0 projects: minor for breaking.
- Move Unreleased entries under the new version heading with today's date, grouped Added / Changed / Fixed / Security.
- Bump the version in the manifest (`package.json`, `pyproject.toml`, `Cargo.toml`, `*.csproj`, `pubspec.yaml`, `mix.exs`…) and anywhere else `project.md` says.
- Commit: `chore(release): v<version>`. Tag: `v<version>`.

## Step 3: Build and verify artefact

- Run the build. For containerised projects: build the image, run it locally, hit `/health`, scan the image (`trivy image` if available; otherwise note skipped).
- `scale`: generate SBOM (`syft` or ecosystem tool) and attach to the release.

## Step 4: Deploy

Use the platform in `project.md`. Prefer the platform's CLI or the CI release workflow created by `kickstart-scaffold`. Order for `scale`: staging → smoke test → production. Order for `pet`: production with a smoke test after.

Smoke test: `/health` returns the new version; one authenticated request succeeds; one key user flow from the latest feature spec works.

If the user is not authenticated with the platform, prepare everything (tag pushed, release notes written) and give the exact deploy command.

## Step 5: Post-release

- Watch the error tracker and logs for 10 minutes (ask the user to confirm, or poll if a CLI is available). Error rate up or health failing → execute the rollback section of the runbook immediately and say so.
- Create the forge release (GitHub/GitLab) with the changelog section as the body.
- Update `.kickstart/project.md`: `last_release: v<version> <date>`, `last_score`.
- Update `.kickstart/compliance.md` `last_review` if any row changed.

## Step 6: Report

Under ten lines: version, what shipped (from changelog), where it is running, checks that warned, and the rollback command.

## Rules

- Never skip the secret scan or the vulnerability scan to make a date. In advised mode you may proceed, but it is written in the report.
- Never deploy with a failing test, even in advised mode, without the user typing "proceed anyway".
- Never release on a Friday evening for `scale` without saying so; offer Monday.
- Keep release commits free of unrelated changes.

Wersje

W bazie nie ma innych skilli o nazwie kickstart-release.

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

  • 100release-checklist
    Układa listę kontrolną wydania i plan decyzji go/no-go: wersjonowanie, bramki CI, migracje, stopniowe wdrożenie i plan wycofania.
  • 90ship
    Wydaje bieżący stan projektu: sprawdza gotowość, podbija wersję i tag, dopisuje wpis do changelogu, wdraża i przygotowuje szkic ogłoszenia.
  • 100kickstart-guardrails
    Instaluje zabezpieczenia projektu: hooki git, bramki CI i reguły agentów, które nie pozwolą wysłać sekretów do repozytorium.
  • 100releasing
    Prowadzi pełny cykl wydania: podniesienie wersji, CHANGELOG, rozbudowane notatki do wydania, tag i publikację.
  • 100version-release
    Podbija wersję, tworzy tag wydania i wypycha tag do repozytorium.
  • 100hatch3r-release
    Przygotowuje wydanie: podniesienie wersji, changelog, tagowanie i weryfikacja wdrożenia na produkcji.

Uwagi i zgłoszenia

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