Skip to content
Skills Library
DevOps & cloud · Automation

release-polygraphy

/release-polygraphy

Prepare a Polygraphy release by auditing all changes since the previous release, finalizing or adding the versioned CHANGELOG section, updating polygraphy/__init__.py, validating the release-only diff, and opening a GitLab merge request targeting develop. Use when asked to create, prepare, cut, or publish a new Polygraphy version or release MR.

Repository
tensorrt ↗
Licence
MIT
Last repository change
09.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/collect_release_context.py

What it does and when to use it

Prepare a Polygraphy release by auditing all changes since the previous release, finalizing or adding the versioned CHANGELOG section, updating polygraphy/__init__.py, validating the release-only diff, and opening a GitLab merge request targeting develop. Use when asked to create, prepare, cut, or publish a new Polygraphy version or release MR.

Original author description

Prepare a Polygraphy release by auditing all changes since the previous release, finalizing or adding the versioned CHANGELOG section, updating polygraphy/__init__.py, validating the release-only diff, and opening a GitLab merge request targeting develop. Use when asked to create, prepare, cut, or publish a new Polygraphy version or release MR.

How it works

  1. Collect release context
  2. Choose the version
  3. Write the release entry
  4. Validate
  5. Open the merge request
Original SKILL.md headings · 94 lines, 537 words
SKILL.md preview
---
name: release-polygraphy
description: Prepare a Polygraphy release by auditing all changes since the previous release, finalizing or adding the versioned CHANGELOG section, updating polygraphy/__init__.py, validating the release-only diff, and opening a GitLab merge request targeting develop. Use when asked to create, prepare, cut, or publish a new Polygraphy version or release MR.
---

# Release Polygraphy

Prepare the version-bump merge request only. Do not merge it, create a tag, or publish packages
unless the user separately requests those actions.

## Collect release context

1. Confirm that the working tree is clean. Preserve unrelated user changes and stop if they overlap
   the release files.
2. Fetch `origin/develop` and version tags so the audit uses current remote state.
3. Run:

   ```bash
   python3 .agents/skills/release-polygraphy/scripts/collect_release_context.py
   ```

4. Inspect every non-merge commit and its diff in the reported tag-to-`origin/develop` range. Use
   first-parent merge commits to understand grouping, but do not rely on commit subjects alone.
5. Confirm that the reported previous tag and `polygraphy.__version__` agree. Resolve any mismatch
   before editing release files.

## Choose the version

- If the top of `CHANGELOG.md` contains a `vNext` section, retain its user-visible content and
  replace `vNext` with the selected version and current date.
- Otherwise, select the next version from the unreleased changes, the user's requested release
  scope, and recent Polygraphy release history. Do not assume a compatible feature requires a minor
  increment: Polygraphy has shipped user-visible additions in patch releases. Ask before changing an
  already-selected release version or making a breaking-version decision.
- Use the local date in `YYYY-MM-DD` format and verify that the version/tag does not already exist.

## Write the release entry

Add the new section at the top of `CHANGELOG.md`, after its introduction. Match the established
format exactly:

```markdown
## vX.Y.Z (YYYY-MM-DD)
### Fixed
- User-visible outcome.
```

- Use only applicable headings from `Added`, `Changed`, `Fixed`, `Deprecated`, and `Removed`, in the
  same style and order as nearby releases.
- Keep two blank lines between version sections and wrap bullets consistently with nearby entries.
- Cover every user-visible change in the audited range, including changes whose original commit did
  not update the changelog.
- Describe behavior, affected commands or public APIs, and the user-visible outcome. Omit internal
  bug IDs, commit/MR references, code structure, algorithms, refactors, tests, and CI details.
- Do not list repository tooling, release mechanics, or this skill as Polygraphy product changes.

Update only `__version__` in `polygraphy/__init__.py` to the same version unless repository evidence
shows another release-version source of truth.

## Validate

Run at least:

```bash
python3 -c "import polygraphy; print(polygraphy.__version__)"
git diff --check
git diff -- CHANGELOG.md polygraphy/__init__.py .agents/skills/release-polygraphy
```

Confirm that:

- the imported version exactly matches the changelog heading;
- the release date and previous tag are correct;
- the changelog contains only user-visible changes;
- the diff contains no unrelated edits.

Release-only metadata edits do not require the full runtime test suite. Run additional focused tests
only if the release branch also changes executable product code.

## Open the merge request

1. Create a branch from the refreshed `origin/develop`, using a descriptive name such as
   `dev-<username>-release-X.Y.Z`.
2. Commit the reviewed release diff with a concise release message.
3. Push the branch and create a GitLab merge request targeting `develop`. If no working GitLab CLI
   is available, use Git push options:

   ```bash
   git push -u origin <branch> \
     -o merge_request.create \
     -o merge_request.target=develop \
     -o 'merge_request.title=Release X.Y.Z' \
     -o 'merge_request.description=<summary and validation>'
   ```

4. Verify the pushed branch, target branch, MR title, and MR URL. Report the version, changelog
   summary, validation performed, commit, and MR link to the user.
Files in this package (3)
  • SKILL.md 4 KB
  • agents/openai.yaml 1 KB
  • scripts/collect_release_context.py 5 KB

Versions

The database has no other skills named release-polygraphy.

Database snapshot: 13.11.2026 · package version 5bb2bc0dbe8d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95prepare_release
    Prepare a release by analyzing all changes since the last git tag, updating CHANGELOG.md with categorized entries, inferring the next semantic version, and auditing all documentation for staleness or missing content. Triggered by requests like "prepare release", "bump version",…
  • 86release-prep
    Prepare a JetWhale release — draft the changelog entry and open the release-prep PR. Use when asked to prepare, cut or plan a release, or to write the changelog for a version.
  • 100release
    Create a release branch from dev with version bumps and changelog. Use when the user wants to prepare a new release, bump a version, or cut a release. Triggers on phrases like "release 17.1.2", "cut a release", "prepare a release", "version bump", or just "/release".
  • 100release
    Execute the grill-me-sleek release process. Use this skill when the user wants to publish a new version, create a release, bump version numbers, or says things like "release v0.2.0", "publish a new version", "cut a release", "ship it", or "prepare release". Also use when the…
  • 100release
    Assemble/verify the CHANGELOG section for a release version from the merged-ticket archive, plus a base_branch git-history fallback for tickets merged without an archive entry, bump the version-location files plus any extra refs configured in this repo's .acs/settings.json…
  • 100release
    Prepare and publish a new cryptobot-python release. Use when the user asks to cut a release, bump the package version, update HISTORY.md, create a git tag, or create a GitHub release.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.