Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

release

Cut a new PyPI release — bump version in pyproject.toml, run scripts/publish.sh, tag, and hand off the final `uv publish` step to the user.

In Manus ausführen

Überblick

Cut a new PyPI release — bump version in pyproject.toml, run scripts/publish.sh, tag, and hand off the final `uv publish` step to the user.

Installationsbefehl

npx skills add https://github.com/ImL1s/aigate --skill release

Kopieren Sie diesen Befehl und fügen Sie ihn in Claude Code ein, um den Skill zu installieren

Quelle

ImL1s/aigate

Sterne2

Forks1

Aktualisiert21. April 2026 um 19:22

SKILL.md

readonly

name	release
description	Cut a new PyPI release — bump version in pyproject.toml, run scripts/publish.sh, tag, and hand off the final `uv publish` step to the user.
disable-model-invocation	true

Release flow for aigate. Ask the user for the new version first (e.g. 0.2.0) — never pick it yourself.

Steps

Confirm target version with the user. Current version lives in pyproject.toml under [project] version.
Bump version in pyproject.toml:
```
# Edit pyproject.toml — change the `version = "X.Y.Z"` line only
```
Nothing else is version-pinned; no other files need updating.
Run the pre-publish check (tests + lint + format + build):
```
cd "$CLAUDE_PROJECT_DIR"
./scripts/publish.sh
```
This runs pytest, ruff check, ruff format --check, and uv build. Stop on any failure — do not proceed.

Commit and tag:

git add pyproject.toml
git commit -m "release: vX.Y.Z"
git tag "vX.Y.Z"

Stop and hand off. Report:
- Build artifacts in dist/
- The exact commands the user must run manually:
```
git push && git push --tags
uv publish --token $PYPI_TOKEN
```

Never run uv publish or git push yourself — the user owns those.

Mehr aus diesem Repository

gleiches Repository

add-backend

ImL1s/aigate

Scaffold a new AI backend that implements AIBackend.analyze() — add file under src/aigate/backends/, register in BACKEND_MAP, wire unit tests. Use when adding support for a new AI model / provider.

2026-04-212

e2e

ImL1s/aigate

Run only the E2E test suite (no full 705-test unit battery). Two modes — Docker-sandboxed (scripts/run-e2e.sh) or direct pytest (tests/e2e/).

2026-04-212

aigate-check

ImL1s/aigate

Check any package for supply chain attacks before installing. Use when: pip install, npm install, yarn add, pnpm add, cargo add, gem install, composer require, flutter pub add, go get, dotnet add package. Also use when someone suggests installing a package or dependency. ALWAYS run this before installing anything — no exceptions.

2026-03-292

aigate-scan

ImL1s/aigate

Scan a lockfile or requirements file for supply chain attacks. Use when: reviewing requirements.txt, package-lock.json, Cargo.lock, Gemfile.lock, composer.lock, pubspec.lock, go.sum, yarn.lock, pnpm-lock.yaml. Also use when auditing project dependencies or onboarding to a new codebase. ALWAYS run this when you see a lockfile or dependency manifest.

2026-03-292

check-package

ImL1s/aigate

Analyze a package with aigate CLI (static pre-filter + optional AI analysis). Usage: /check-package <name> [version] [ecosystem]

2026-03-282

verify

ImL1s/aigate

Run lint, format check, and all tests to verify code quality before committing.

2026-03-282

Quelle

ImL1s

ImL1s/aigate

GitHub-Repository öffnen Creator-Repositorys ansehen

Installationsbefehl

Download

In Manus ausführen

Nützlich fürSOC

SoftwareentwicklerInformatik- und Mathematikberufe15-1252L4

name	release
description	Cut a new PyPI release — bump version in pyproject.toml, run scripts/publish.sh, tag, and hand off the final `uv publish` step to the user.
disable-model-invocation	true

Release flow for aigate. Ask the user for the new version first (e.g. 0.2.0) — never pick it yourself.

Steps

Confirm target version with the user. Current version lives in pyproject.toml under [project] version.
Bump version in pyproject.toml:
```
# Edit pyproject.toml — change the `version = "X.Y.Z"` line only
```
Nothing else is version-pinned; no other files need updating.
Run the pre-publish check (tests + lint + format + build):
```
cd "$CLAUDE_PROJECT_DIR"
./scripts/publish.sh
```
This runs pytest, ruff check, ruff format --check, and uv build. Stop on any failure — do not proceed.

Commit and tag:

git add pyproject.toml
git commit -m "release: vX.Y.Z"
git tag "vX.Y.Z"

Stop and hand off. Report:
- Build artifacts in dist/
- The exact commands the user must run manually:
```
git push && git push --tags
uv publish --token $PYPI_TOKEN
```

Never run uv publish or git push yourself — the user owns those.