Add release-pycel2sql agent skill#14
Merged
richardwooding merged 1 commit intomainfrom Apr 28, 2026
Merged
Conversation
Captures the procedure for cutting a pycel2sql release. The release flow is shorter than upstream cel2sql Go's (no manual CHANGELOG — release.yml generates notes from `git log $PREV_TAG..$TAG`) and simpler than cel2sql4j Java's (no GPG signing, no Sonatype staging — PyPI uses OIDC trusted publishing; hatch-vcs reads the tag, no version file to drift). Layout under .claude/skills/release-pycel2sql/: - SKILL.md (~80 lines) — quick start, semver decision, common slip-ups (lightweight tag, hatch-vcs version-file confusion, pre-release qualifier shape), PyPI OIDC notes, post-tag verification checklist. - scripts/release_preflight.sh — validates working tree + branch + sync state, CI status on origin/main, open Dependabot PRs (soft warning), release-notes preview from git log; if a version is supplied, validates the format and prints tag commands. Modeled on cel2sql4j's release_preflight.sh. The skill deliberately omits a separate references/ directory — the relevant config files (release.yml, ci.yml, pyproject.toml) are small enough to read directly when needed. Lints clean against .claude/skills/skill-authoring/scripts/lint_skill.py. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fourth and final maintenance skill (per the plan). Captures the procedure for cutting a pycel2sql release.
The release flow is shorter than upstream cel2sql Go's (no manual CHANGELOG — `release.yml` generates notes from `git log $PREV_TAG..$TAG`) and simpler than cel2sql4j Java's (no GPG signing, no Sonatype staging — PyPI uses OIDC trusted publishing; hatch-vcs reads the tag at build time, so there's no version file to drift).
Layout
The skill deliberately omits a separate `references/` directory — the relevant config files (`release.yml`, `ci.yml`, `pyproject.toml`) are small enough to read directly when needed.
Smoke test
Running `bash .claude/skills/release-pycel2sql/scripts/release_preflight.sh` from `main` produces:
```
=== Working tree ===
OK: on main
OK: working tree clean
OK: in sync with origin/main (...)
=== Commits since v0.2.0 (release-notes preview) ===
a7db259 Add skill-authoring agent skill (#10)
167eb4f ci: restrict GITHUB_TOKEN to contents:read in CI workflow (#9)
... (10 commits since previous tag)
=== CI on origin/main HEAD ===
success CI
=== Open Dependabot PRs ===
OK: no open Dependabot PRs
=== Summary: 0 error(s), 0 warning(s) ===
```
(I ran it on the feature branch, where it correctly errored on the branch + dirty-tree checks. Confirmed working from main produces the clean output above.)
Lint
```
$ python .claude/skills/skill-authoring/scripts/lint_skill.py .claude/skills/release-pycel2sql/
0 error(s), 0 warning(s)
```
Test plan
🤖 Generated with Claude Code