release
/release
Tworzy wydania GitHub dla wtyczek cc-foundry: osobne tagi, notatki jako changelog i publikację po wypchnięciu.
- Autor
- xobotyi ↗
- Repozytorium
- cc-foundry ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 26.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 2
Brak sygnałów. Repozytorium zmienione 26.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Tworzy wydania GitHub dla wtyczek cc-foundry: osobne tagi, notatki jako changelog i publikację po wypchnięciu.
Oryginalny opis (EN)
GitHub release creation for cc-foundry plugins: per-plugin tags, release notes as the changelog, and post-push publishing. Invoke whenever task involves pushing commits to master, releasing or publishing a plugin version, bumping plugin versions, or writing release notes.
Jak działa
- When to Release
- Identify What to Release
- Tag and Title Scheme
- Release Notes
- Create the Release
- Verify
Podgląd SKILL.md
--- name: release description: >- GitHub release creation for cc-foundry plugins: per-plugin tags, release notes as the changelog, and post-push publishing. Invoke whenever task involves pushing commits to master, releasing or publishing a plugin version, bumping plugin versions, or writing release notes. --- # Plugin Releases Every plugin version bump that lands on master ships with a GitHub release. The release notes are the plugin's changelog — there are no CHANGELOG.md files (see [ADR 1.5](/design-docs/adr/1.5-plugin-changelog.md)). A pushed version bump without a release is an incomplete ship. ## When to Release - After every push to master, check the pushed range for plugin version bumps; create one release per plugin whose version changed. - The user's authorization to push covers release creation — do not ask a second time. - Repo-level changes that bump no plugin version (ADRs, root docs, `.dev/` tooling, this skill) get no release. - Several plugins bumped in one push → one release each. ## Identify What to Release 1. Find bumped plugins in the pushed range: `git diff <old-origin-head>..origin/master -- '*/plugin.json'`. When the old head is unknown, compare each plugin's `plugin.json` version against its latest `<plugin>-v*` tag from `gh release list`. 2. For each bumped plugin, resolve: - the pushed commit that changed its `plugin.json` version — the release target - the previous release tag `<plugin>-v*`, if any — the notes range and compare-link anchor 3. Collect source material: `git log <prev-tag>..<target> -- plugins/<name>/` plus the diff of that range. For a first release, use the commits of the bump itself. ## Tag and Title Scheme - **Tag** — `<plugin>-v<X.Y.Z>`, e.g. `the-coder-v1.5.0` - **Title** — `<plugin> v<X.Y.Z>`, e.g. `the-coder v1.5.0` - **Target** — the pushed commit that landed the version bump, as its **full 40-character SHA**. GitHub rejects an abbreviated SHA with `HTTP 422 Validation Failed` and the misleading trio `tag_name is not a valid tag`, `Release.target_commitish is invalid`, `Published releases must have a valid tag`. Resolve it with `git rev-parse <short-sha>`; a branch name also works. - Never run `git tag` — `gh release create` creates the tag on the remote at publish time. ## Release Notes Written for people who install the plugin, not for repo contributors. <prerequisite> Invoke `the-writer:humanize` before drafting. All release prose — the lead sentence and every bullet — is written in its writing mode and passes its self-audit before `gh release create`. If the skill is unavailable, ask the user to install the `the-writer` plugin before proceeding. </prerequisite> - Lead with one sentence stating what the release is about. - Segment by changed component, one `###` section per component: ``### `<name>` skill``, ``### `<name>` output style`` — same pattern for hooks, commands, and agents. A plugin bumps its version even when a single component moved; the segments tell the installer exactly which parts did. - Plugin-wide changes that belong to no component (README, packaging, licensing) go under a final `### Plugin` section. - Within a segment, prefix each bullet with its change type in bold — `**Added:**`, `**Changed:**`, `**Fixed:**`, `**Removed:**` — ordered Added → Changed → Fixed → Removed. - Each bullet states the change and, where not obvious, why it matters to a plugin user. - Distill from commit messages and the diff. Never paste a commit list, shortlog, or auto-generated notes. - No session artifacts (test counts, CI status) and no repo-internal jargon that means nothing to an installer. - End with a compare link when a previous tag exists: `**Full diff:** https://github.com/xobotyi/cc-foundry/compare/<prev-tag>...<new-tag>` - First release of a plugin: no compare link; notes cover this version's changes only, not the plugin's history. ### Example ```markdown Sharpens commit-message validation and adds trailer support. ### `commit-message` skill - **Added:** `Task:` and `Refs:` trailer validation — malformed trailers now fail validation instead of landing silently. - **Changed:** subject-length limit aligned with git conventions: 50 soft / 72 hard (was a flat 72). ### `commit` skill - **Fixed:** validator crashed on commit messages containing unescaped backticks. **Full diff:** https://github.com/xobotyi/cc-foundry/compare/git-commit-v1.1.3...git-commit-v1.1.4 ``` ## Create the Release Write the notes to a scratchpad file first — `--notes-file` avoids shell-quoting damage: ```bash gh release create <plugin>-v<X.Y.Z> \ --target <bump-commit-sha> \ --title "<plugin> v<X.Y.Z>" \ --notes-file <path-to-notes.md> ``` - To stage a release for user review, add `--draft` (visible to collaborators only; the tag is created at publish, not at draft creation). Publish with `gh release edit <tag> --draft=false` — re-set `--target` to the bump commit first if the draft was created before the push. ## Verify - `gh release view <tag>` — confirm title, target, and notes. - Cross-check: every plugin bumped in the pushed range has a release; `plugin.json` version equals the latest tag.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · xobotyi/cc-foundry | 100 | MIT |
| josephfung/curia | 100 | MIT |
| max-sixty/worktrunk | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| gtapps/hermitd | 100 | MIT |
| anthony-chaudhary/fak | 100 | Apache-2.0 |
| tractorjuice/arc-kit | 100 | MIT |
| drvoss/everything-copilot-cli | 100 | MIT |
| sma1lboy/rove | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 05a89ddf85e3 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100semantic-release
Automatyzuje wersjonowanie i publikację: czyta komunikaty commitów, wybiera kolejną wersję semantyczną, pisze notatki wydania i changelog, taguje commit, publikuje do npm i tworzy release na GitHubie. - 100releasing
Prowadzi pełny cykl wydania: podniesienie wersji, CHANGELOG, rozbudowane notatki do wydania, tag i publikację. - 100releasing-plugin-versions
Prowadzi wydanie nowej wersji wtyczki w marketplace: podniesienie wersji, tagi git i publikacja wydań na GitHubie. - 100release-notes
Pisze notatki do wydania lub wpis do changelogu na podstawie historii git od ostatniego tagu. - 100release-this
Obsługuje pełne wydanie wtyczki powerball-harness: build, walidację, podniesienie wersji, CHANGELOG, tag i GitHub Release. - 100release-guru
Przygotowuje, planuje lub odzyskuje wydanie cnative-skills: wersje, tagi rc, notatki i wycofanie wydania po błędzie.