chore: add release skill - #139
Conversation
Cutting a release here was undocumented tribal knowledge. Every actively released cuioss Java repo now carries .claude/skills/release/SKILL.md. The skill is derived from this repo's own .github/project.yml rather than copied verbatim: the version scheme, the consumer list and the artifact coordinates all differ per repo, and those are exactly the facts an operator has to get right. Points it records that cost time elsewhere in the org: - Unresolved review threads block the merge even when every check is green. That state reads like a branch-protection problem and is not one. - A published release can be left as a draft, which is invisible to consumers - Step 11 checks isDraft and verifies the artifact actually resolves from Maven Central, rather than trusting the workflow's exit status. - Comment and thread enumeration paginate; a truncated list looks complete while hiding the thread that is blocking the merge. - allowed-tools includes AskUserQuestion, which the skill needs at the one step where it insists on asking. Co-Authored-By: Claude <noreply@anthropic.com>
There was a problem hiding this comment.
Sorry @OliverWolffGIP, you've used your own review budget of 250,000 diff characters for the last 7 days.
You can request another review in 3 days and 9 hours by commenting @sourcery-ai review. Upgrade to get a review now.
|
Important Review skippedAuto reviews are limited based on label configuration. 🚫 Excluded labels (none allowed) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: cuioss/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Warum
Ein Release in diesem Repo zu schneiden war undokumentiertes Erfahrungswissen. Alle aktiv releaseten cuioss-Java-Repos tragen jetzt
.claude/skills/release/SKILL.md.Nicht kopiert, sondern abgeleitet
Das Skill wird aus der
.github/project.ymldieses Repos erzeugt — Versionsschema, Consumer-Liste und Artefakt-Koordinaten unterscheiden sich pro Repo, und genau die muss ein Operator richtig treffen.Wo
current-versionundnext-versionzwei plausible nächste Versionen zulassen, sagt das Skill das explizit und fragt, statt zu raten.Was es festhält — jeder Punkt hat anderswo Zeit gekostet
isDraftund verifiziert, dass das Artefakt tatsächlich von Maven Central auflöst — statt dem Exit-Status des Workflows zu vertrauen.allowed-toolsenthältAskUserQuestion— genau an der Stelle, an der das Skill auf Nachfragen besteht, konnte es das vorher nicht.Reine Dokumentation — keine Build- oder Quellcode-Änderung.