gh-deps-intel
Gh Deps Intel
Use this as the canonical dependency-upgrade workflow skill. The shared deps-workbench helpers provide lightweight preflight inventory, classification, and usage mapping; this skill remains the deeper GitHub-aware analysis and reporting engine. This skill absorbs the former dep-upgrade-spec role.
Invocation Defaults
- Explicit invocation with upgrade language such as "fully upgrade", "apply the upgrade", or a specific target package defaults to
execute. - Explicit invocation without an implementation request defaults to
plan. - In
execute, still stop if auth, package-manager access, or repo safety checks fail.
Tool Routing (MUST FOLLOW)
- If you need a cheap preflight, run the shared helpers first:
/home/bjorn/.codex/skill-support/bin/deps-workbench inventory --cwd <repo> --out <json>/home/bjorn/.codex/skill-support/bin/deps-workbench classify --input <json> --out <json>/home/bjorn/.codex/skill-support/bin/deps-workbench usage-scan --cwd <repo> --packages <pkg...> --out <json>
- If the user explicitly requests
gh api/CLI only, usescripts/gh_release_diff.py,scripts/gh_compare_notes.py, orscripts/gh_rate_limit_diag.pydirectly. - For single-package requests ("fully upgrade X package"), use
scripts/gh_deps_intel.py package --dependency <name>. - Otherwise, use
scripts/gh_deps_intel.py fullas the single orchestrator path (REST-first with GraphQL fallback for release retrieval).
More from bjornmelin/dev-skills
streamdown
|
13zod-v4
Expert guidance for Zod v4 schema validation in TypeScript. Use when designing schemas, migrating from Zod 3, handling validation errors, generating JSON Schema/OpenAPI, using codecs/transforms, or integrating with React Hook Form, tRPC, Hono, or Next.js. Covers all Zod v4 APIs including top-level string formats, strictObject/looseObject, metadata, registries, branded types, and recursive schemas.
9vitest-dev
World-class Vitest QA/test engineer for TypeScript + Next.js (local + CI performance focused)
8docker-architect
SOTA Docker/Compose architecture, implementation, refactor, and security hardening. Use when working on containerization tasks such as creating or rewriting Dockerfiles, docker-compose files, buildx/bake configs, .dockerignore, and CI pipelines for build/test/scan/publish; auditing existing container setups for security, correctness, size/perf, and best practices (least privilege, non-root, minimal images, pinned base images, BuildKit secrets, healthchecks); debugging Docker build/run issues; or designing dev vs prod compose workflows across services (DB/cache/queues) with correct networking, volumes, secrets, and resource limits.
7pytest-dev
World-class pytest engineer for Python: write/refactor tests, fix flakiness, design fixtures/markers, add coverage, speed up suites (collection/runtime), and optimize CI (GitHub Actions sharding, xdist parallelism, caching). Use when asked about pytest best practices, pytest 9.x features (subtests, strict mode, TOML config), pytest plugins (xdist/cov/asyncio/mock/httpx), or test performance/CI tuning.
6notebook-ml-architect
>
5