Skill

pactkit-release

Version release: snapshot, archive, Git tag, and GitHub Release

Install

npx claudepluginhub pactkit/claude-code-plugin --plugin pactkit

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Version release management — update versions, snapshot architecture, create Git tags, and publish GitHub Releases.

SKILL.md

Similar Skills

kotlin-ktor-patterns

Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.

everything-claude-code

163.2k

deep-research

Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.

everything-claude-code

163.2k

inventory-demand-planning

Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.

everything-claude-code

163.2k

Stats

Parent Repo Stars4

Parent Repo Forks0

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

PactKit Release

Version release management — update versions, snapshot architecture, create Git tags, and publish GitHub Releases.

When Invoked

/project-release command: VERSION is passed explicitly from the command's pre-flight check.

Standalone / legacy path: VERSION is not provided — auto-detected from pyproject.toml.

Version Parameter

If VERSION is provided (e.g., by /project-release): use it directly, skip auto-detection.

If version is not provided: auto-detect by running git diff HEAD~1 pyproject.toml | grep version and extracting the new value.

Protocol

1. Version Update

Run update_version "$VERSION" via pactkit-board skill.

Update the project's package manifest (e.g., pyproject.toml, package.json).

Backfill Specs: run pactkit backfill-release $VERSION to replace Release: TBD in completed specs.

2. Architecture Snapshot

Run visualize (all three modes: file, class, call).

Run snapshot "$VERSION" via pactkit-board skill.

Result: graphs saved to docs/architecture/snapshots/{version}_*.mmd.

3. Git Operations

Run archive via pactkit-board skill.

Commit: git commit -am "chore(release): $VERSION".

Tag: git tag $VERSION.

4. GitHub Release (Conditional)

Check config: Read pactkit.yaml for release.github_release.

If release.github_release: true: proceed with GitHub Release creation.
If release.github_release: false or section missing: log "GitHub Release: SKIP — not configured" and stop.

Extract the [$VERSION] section from CHANGELOG.md as release notes.

Create a GitHub Release: gh release create $VERSION --title "$VERSION" --notes "$NOTES".

Verify: gh release view $VERSION confirms the release exists and is marked Latest.

PactKit Release

Version release management — update versions, snapshot architecture, create Git tags, and publish GitHub Releases.

When Invoked

/project-release command: VERSION is passed explicitly from the command's pre-flight check.
Standalone / legacy path: VERSION is not provided — auto-detected from pyproject.toml.

Version Parameter

If VERSION is provided (e.g., by /project-release): use it directly, skip auto-detection.
If version is not provided: auto-detect by running git diff HEAD~1 pyproject.toml | grep version and extracting the new value.

Protocol

1. Version Update

Run update_version "$VERSION" via pactkit-board skill.
Update the project's package manifest (e.g., pyproject.toml, package.json).
Backfill Specs: run pactkit backfill-release $VERSION to replace Release: TBD in completed specs.

2. Architecture Snapshot

Run visualize (all three modes: file, class, call).
Run snapshot "$VERSION" via pactkit-board skill.
Result: graphs saved to docs/architecture/snapshots/{version}_*.mmd.

3. Git Operations

Run archive via pactkit-board skill.
Commit: git commit -am "chore(release): $VERSION".
Tag: git tag $VERSION.

4. GitHub Release (Conditional)

Check config: Read pactkit.yaml for release.github_release.
- If release.github_release: true: proceed with GitHub Release creation.
- If release.github_release: false or section missing: log "GitHub Release: SKIP — not configured" and stop.
Extract the [$VERSION] section from CHANGELOG.md as release notes.
Create a GitHub Release: gh release create $VERSION --title "$VERSION" --notes "$NOTES".
Verify: gh release view $VERSION confirms the release exists and is marked Latest.