Menu
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.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
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/).
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.
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.
Analyze a package with aigate CLI (static pre-filter + optional AI analysis). Usage: /check-package <name> [version] [ecosystem]
Run lint, format check, and all tests to verify code quality before committing.
| 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.
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:
dist/git push && git push --tags
uv publish --token $PYPI_TOKEN
Never run uv publish or git push yourself — the user owns those.