skills.rest
tetherto
tethertoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

commit-trace

Trace npm package versions containing a specific commit SHA and analyze transitive dependencies.

395|94|Updated Jan 3, 2026
Search Tags:#npm#commit#release#package#dependency#version
One-click install
npx skills add https://github.com/tetherto/qvac --skill commit-trace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: commit-trace
Source: https://github.com/tetherto/qvac/tree/main/packages/ocr-onnx/.agent/skills/commit-trace
Command: npx skills add https://github.com/tetherto/qvac --skill commit-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill allows users to trace a commit SHA to determine which npm package versions include it, providing clarity on publish history and transitive dependencies.

Core Features & Use Cases

  • Commit Validation and Context: Verify the existence and view details of a specific commit.
  • Package Impact Analysis: Map the commit to affected packages and identify the earliest release versions containing it.
  • Dependency Resolution: Analyze how affected packages are integrated into the SDK, including version ranges, publish timestamps, and whether they are included at release or only on fresh installs.
  • Use Case: Developers can track whether a bug fix in a particular commit is available in the npm releases and understand transitive dependency impacts across SDK versions.

Quick Start

Provide a commit SHA to see which versions of packages in the repository include it and whether they are present at release time or only in development snapshots.

Frequently Asked Questions about commit-trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find which npm package version includes a specific commit?▼

To find which npm package version includes a specific commit, provide the commit SHA to map affected packages and identify the earliest release versions containing it. This traces the commit directly to its published npm releases.

What is the best way to check if a bug fix commit is available in an npm release?▼

Checking if a bug fix commit is available in an npm release involves tracing the commit SHA to determine which package versions include it. This provides clarity on publish history and verifies the fix's release status.

How do I analyze transitive dependencies for a specific npm package commit?▼

To analyze transitive dependencies for a specific npm package commit, the tool resolves how affected packages integrate into the SDK. It evaluates version ranges, publish timestamps, and inclusion at release or fresh install.

Can I track the publish timestamp of an npm package relative to a specific commit?▼

Yes, you can track the publish timestamp of an npm package relative to a specific commit by assessing the timing of package releases. This maps the commit SHA to its affected packages and evaluates release chronology.

Why are my npm transitive dependencies only included in development snapshots and not at release time?▼

Transitive dependencies may only appear in development snapshots instead of at release time based on version ranges and publish timestamps. Analyzing the commit SHA reveals whether affected packages are included at release or only on fresh installs.

Related Skills

Explore More Software Engineering Skills→
dotnetdotnet
710

update-roslyn-version

Update Roslyn dependency versions in the razor repository and refresh commit SHAs.

Official
Intermediate
FFOO6866FFOO6866

deployment-git

Coordinate Git workflows and CI/CD pipelines to publish multi-package SDKs to PyPI.

Community
Advanced
s1366560s1366560
5

gitnexus-impact-analysis

Analyze code change impact by mapping upstream dependencies and affected execution flows.

Community
Intermediate
baekenoughbaekenough
34

npm-publish

Automate npm package publishing with pre-publish validation and dry-run checks.

Community
Advanced