Loading...
Loading...
Found 12 Skills
Initialize, reindex, or manage the git-pkgs dependency database. Use when setting up git-pkgs in a repository for the first time, updating the database after pulling new commits, or checking database status.
Track dependency change history, find who added each dependency, and understand why packages were introduced. Use when investigating when a dependency was added or changed, who introduced it, or which commits modified dependencies.
Add, remove, update, install, or vendor dependencies using the project's detected package manager. Use when the user wants to modify their dependencies.
List, search, and locate dependencies in the current project. Use when exploring what packages are installed, finding where a dependency is declared, searching for packages by name pattern, or viewing the dependency tree.
Scan dependencies for known vulnerabilities using OSV. Use when checking for CVEs, reviewing security posture, or investigating who introduced a vulnerable dependency.
Compare dependencies between commits, branches, or the working tree. Use when reviewing what dependencies changed in a PR, between releases, or since a specific commit.
Show license information for all project dependencies. Use when checking license compliance, reviewing license compatibility, or auditing for copyleft or missing licenses.
Find dependencies with newer versions available or that haven't been updated in a long time. Use when checking for available updates, finding stale packages, or planning a dependency update cycle.
Generate a Software Bill of Materials in CycloneDX or SPDX format. Use when producing SBOMs for compliance, supply chain transparency, or software composition analysis.
Interact with GitHub, GitLab, Gitea, Forgejo, Codeberg, and Bitbucket repositories through one CLI. Use instead of `gh` or `glab` when the git remote is not github.com, when working against a self-hosted forge, or when the same workflow needs to run unchanged across forges. Covers pull/merge requests, issues, releases, CI pipelines, labels, and repo management.
Evaluate a package before adding it as a dependency. Checks registry metadata, adoption, maintenance, security posture, and license. Use when assessing whether a package is trustworthy, comparing alternatives, or reviewing a new dependency.
Detect a project's toolchain, languages, package managers, test runners, linters, and conventions. Use when starting work on a project, onboarding to a codebase, or checking what tools are configured. Also detects tooling gaps and fetches external metadata.