メニュー
Analyze a package with aigate CLI (static pre-filter + optional AI analysis). Usage: /check-package <name> [version] [ecosystem]
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | check-package |
| description | Analyze a package with aigate CLI (static pre-filter + optional AI analysis). Usage: /check-package <name> [version] [ecosystem] |
Analyze the package specified in $ARGUMENTS using the aigate CLI.
Parse arguments: first arg is package name, optional second is version, optional third is ecosystem (default: pypi).
cd "$CLAUDE_PROJECT_DIR"
# Run with AI analysis if backends available, fallback to --skip-ai
.venv/bin/aigate check $ARGUMENTS || .venv/bin/aigate check $ARGUMENTS --skip-ai
After analysis, summarize:
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/).
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.
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.
Run lint, format check, and all tests to verify code quality before committing.