Agent skill

Commit Trace

by tetherto in tetherto/qvac

Trace a commit to its published npm versions, including transitive SDK resolution with time-aware accuracy

Apache-2.0Auto-check passedAI & LLM Engineering

Install Commit Trace

skills CLI
$ npx skills add tetherto/qvac --skill commit-trace -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tetherto/qvac commit-trace --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/tetherto/qvac.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/ocr-ggml/.agent/skills/commit-trace .claude/skills/commit-trace && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
commit-trace
GitHub stars
674
Token cost
~1.7k tokens
SKILL.md length
722 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
Apache-2.0

At a glance

Trace a commit to its published npm versions, including transitive SDK resolution with time-aware accuracy

  • Works in 7 steps: Validate the Commit → Identify Affected Packages → Find Direct Release Versions → …
  • AI & LLM Engineering work in your project
  • SKILL.md covers Usage, Step 1: Validate the Commit, Step 2: Identify Affected… and Step 3: Find Direct Release…, plus 5 more sections
  • Calls git and npm

What it does

Commit Trace is an agent skill from tetherto/qvac. Trace a commit to its published npm versions, including transitive SDK resolution with time-aware accuracy

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering. It works with npm and llama.cpp. The repository describes itself as: Open-source local AI SDK - run AI on-device with no cloud, no API keys. Supports GGUF, RAG, image, music, and video generation, speech-to-text, P2P inference, and more… The licence is Apache-2.0.

When your agent uses it

  • AI & LLM Engineering work in your project

Example prompts

  • “/commit-trace”

Requirements

  • Node.js

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Validate the Commit
  2. Identify Affected Packages
  3. Find Direct Release Versions
  4. Get npm Publish Timestamps
  5. Transitive Resolution via SDK
  6. Generate Report
  7. Reverse Lookup Mode (Optional)

What it can do on your machine

Read from SKILL.md and the folder at commit d92f697. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Commit Trace loads about 1.7k tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 722 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~30
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from tetherto/qvac at commit d92f697, republished under its Apache-2.0 licence (© tetherto). 722 words, ~1,711 tokens.

Download SKILL.mdSave it as .claude/skills/commit-trace/SKILL.md (or your agent's skills folder).
name
commit-trace
description
Trace a commit to its published npm versions, including transitive SDK resolution with time-aware accuracy
argument-hint
<commit-sha>
disable-model-invocation
true

Commit Trace — Find Where a Commit is Published

Given a commit SHA, determines exactly which npm package versions contain it — both directly and transitively via the SDK. Accounts for publish timestamps to give time-accurate resolution answers.

Usage

/commit-trace <commit-sha>
/commit-trace a1b2c3d
/commit-trace a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6e7f8a9b0

Step 1: Validate the Commit

Verify the commit exists:

bash
git cat-file -t <sha>

If invalid, report and stop.

Show the commit summary for context:

bash
git log --oneline -1 <sha>

Step 2: Identify Affected Packages

Get the list of files changed by this commit:

bash
git diff-tree --no-commit-id --name-only -r <sha>

Map each changed file path to its package by matching packages/<dir>/ prefixes.

For each affected directory, read packages/<dir>/package.json to get:

  • The npm package name (e.g., @qvac/llm-llamacpp)
  • The current version

Build a list of (directory, npm-name) pairs. If no packages/ files were touched, report "this commit does not affect any publishable package" and stop.

Step 3: Find Direct Release Versions

For each affected package, find which release tags contain the commit:

bash
git tag --contains <sha>

Filter to tags relevant to this package. Tag naming conventions in this repo:

  • llamacpp-llm-v0.12.1 for @qvac/llm-llamacpp (package llm-llamacpp)
  • ocr-ggml-v0.11.0 for @qvac/ocr-ggml
  • whispercpp-v0.5.0 for @qvac/transcription-whispercpp
  • Tags vary per package — match by inspecting existing tags for the package

Also check release branches that contain the commit:

bash
git branch -r --contains <sha>

Filter to origin/release-* branches relevant to this package.

From the tags and branches, determine the earliest version that contains this commit.

Step 4: Get npm Publish Timestamps

For each affected package, query npm for all published versions with their timestamps:

bash
npm view <npm-name> time --json

This returns a JSON object like {"0.12.0": "2026-03-01T...", "0.12.1": "2026-03-10T...", ...}.

Cross-reference: for the version(s) found in Step 3, get their exact publish dates.

If the commit is NOT in any released version yet, report it as unreleased — only on main (dev builds) or a feature branch.

Step 5: Transitive Resolution via SDK

This is the critical step. The SDK (@qvac/sdk) depends on addon packages with caret ranges (e.g., "@qvac/llm-llamacpp": "^0.12.1").

For each affected package that the SDK depends on:

5a. Find the SDK's version range

Read packages/sdk/package.json and find the dependency entry for this package. Note the semver range (e.g., ^0.12.1).

5b. Get all SDK release versions and their publish dates
bash
npm view @qvac/sdk time --json
Show full SKILL.md (386 more words)Show less
5c. For each SDK version, determine the answer to three questions

For each published SDK version:

  1. Does the SDK's semver range allow the addon version containing the commit?

    • Read the SDK's package.json at that SDK's release tag/branch to get the pinned range
    • Check if the addon version from Step 3 satisfies that range
    • CRITICAL — 0.x caret semantics: When the major version is 0, caret (^) locks to the minor version, NOT the major. For example:
      • ^0.1.5 → >=0.1.5 <0.2.0 (will NOT pick up 0.2.0, 0.3.0, etc.)
      • ^0.12.1 → >=0.12.1 <0.13.0 (will NOT pick up 0.13.0)
      • ^1.2.3 → >=1.2.3 <2.0.0 (normal behavior for major >= 1)
    • If the range doesn't allow it, the answer is NO regardless of timing. Report that the SDK needs a dependency bump.
  2. Was the addon version published before this SDK version?

    • Compare publish timestamps from npm
    • If the addon version was published AFTER the SDK version, then even if the range allows it, users who installed the SDK at release time would NOT have gotten this addon version
  3. Would a fresh install TODAY resolve to the addon version?

    • Check if a newer addon version exists that also satisfies the range
    • The latest version satisfying the range is what npm would resolve today
5d. Check lock file (if accessible)

For the SDK's release branch, check if a lock file exists that pins the exact addon version:

bash
git show origin/release-sdk-<version>:packages/sdk/package-lock.json

or

bash
git show origin/release-sdk-<version>:packages/sdk/npm-shrinkwrap.json

If a lock file exists, it tells us exactly what shipped. This is the ground truth.

Step 6: Generate Report

Present findings in this format:

Commit: <sha> "<commit message>"
Date: <commit date>

━━━ Direct Packages ━━━

@qvac/llm-llamacpp
  ✅ Released in: v0.12.2 (published 2026-03-15)
  ⏳ Also in dev: 0.13.0-dev.4 (from main)

@qvac/sdk (files touched directly)
  ❌ Not yet released (latest: v0.7.0, commit is after)

━━━ Transitive via @qvac/sdk ━━━

@qvac/llm-llamacpp v0.12.2 → consumed by SDK:

  @qvac/sdk@0.7.0 (published 2026-03-10, pins "^0.12.1")
    Range allows 0.12.2?  ✅ Yes
    0.12.2 existed at SDK publish time?  ❌ No (published 5 days later)
    Fresh install today resolves to?  0.12.2 ✅
    Lock file shipped with?  0.12.1 ❌
    Verdict: ❌ NOT included at release, ✅ included on fresh install today

  @qvac/sdk@0.8.0 (published 2026-03-20, pins "^0.12.1")
    Range allows 0.12.2?  ✅ Yes
    0.12.2 existed at SDK publish time?  ✅ Yes
    Fresh install today resolves to?  0.12.2 ✅
    Lock file shipped with?  0.12.2 ✅
    Verdict: ✅ included at release AND on fresh install

━━━ Summary ━━━

To guarantee this commit:
  • Direct: install @qvac/llm-llamacpp@>=0.12.2
  • Via SDK: install @qvac/sdk@>=0.8.0 (or sdk@0.7.0 with fresh npm install today)

Step 7: Reverse Lookup Mode (Optional)

If the argument looks like a package@version instead of a SHA (contains @):

/commit-trace @qvac/sdk@0.7.0

Reverse the flow:

  1. Find the git tag for that version
  2. Find the previous version's tag
  3. List all commits between the two tags
  4. For each commit, show the one-line summary
  5. Group by affected sub-package

Error Handling

  • Commit not found: Report "commit SHA not found in this repository"
  • No packages affected: Report "this commit only touches non-package files (CI, docs, root config)"
  • Package not on npm: Report "this package has never been published to npm" — it may be internal-only
  • npm registry unreachable: Fall back to git-only analysis (tags and branches), skip timestamp resolution
  • No SDK dependency: If the affected package is not a dependency of the SDK, skip the transitive section entirely

© tetherto, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/ocr-ggml/.agent/skills/commit-trace of tetherto/qvac.

Open the folder on GitHubat commit d92f697

Compare with similar skills

Commit Trace next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Commit Trace compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Commit Trace this skilltetherto/qvac674—~1.7kAutomated safety check: PassApache-2.0
Helmor Bump Vendorsdohooo/helmor1.3k—~2.1kAutomated safety check: PassApache-2.0
Aider DelegateamElnagdy/delegate-skills2.3k2 repos~3kAutomated safety check: PassMIT
Hugging Face LLM Trainerhuggingface/skills11k3 repos~7.2kAutomated safety check: PassApache-2.0
Compromise NLP for JavaScriptspencermountain/compromise12k—~1.8kAutomated safety check: PassMIT
Tavily Search API Integrationandrewyng/context-hub14k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Helmor Bump Vendors

    dohooo/helmor

    Bump or upgrade the pinned versions of Helmor's bundled agent CLIs, SDKs, and supporting binaries — Claude Code + claude-agent-sdk (lockstep), Codex, Cursor SDK, OpenCode, Kimi, Pi, and gh / glab /…

    1.3k GitHub stars~2.1k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Aider Delegate

    amElnagdy/delegate-skills

    Delegate a coding task to Aider (aider) as a background implementer, then review its diff and land it yourself.

    2.3k GitHub starsUsed in 2 repos~3k tokens
    AI & LLM EngineeringAuto-check passed
  • Hugging Face LLM Trainer

    huggingface/skills

    Official

    Trains or fine-tunes language and vision models with TRL or Unsloth on Hugging Face Jobs cloud GPUs, then converts the results to GGUF.

    11k GitHub starsUsed in 3 repos~7.2k tokens
    AI & LLM EngineeringAuto-check passed
  • Compromise NLP for JavaScript

    spencermountain/compromise

    Guide for writing correct code with the compromise rule-based NLP library: tagging, match syntax, in-place transforms and common tasks like tense changes and redaction.

    12k GitHub stars~1.8k tokensUpdated yesterday
    AI & LLM EngineeringAuto-check passed
  • Tavily Search API Integration

    andrewyng/context-hub

    Guides building Tavily integrations for web search, URL extraction, site crawling and AI-assisted research in Python or JavaScript agent and RAG projects.

    14k GitHub stars~1.1k tokensUpdated 4 mo ago
    AI & LLM EngineeringAuto-check passed
  • Qwen Mtp Gguf

    R6410418/Jackrong-llm-finetuning-guide

    Complete agent-ready workflow for Qwen-family MTP or nextn GGUF conversion and release.

    1.7k GitHub stars~1.7k tokensUpdated 2 mo ago
    AI & LLM EngineeringAuto-check passed

More from tetherto/qvac

All 50 skills in this repo
  • Creates a Solutions page in the QVAC documentation website from a real use case, generalizing the case into reusable guidance and registering the page in the site navigation.

    674 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Qv Docs Update

    tetherto/qvac

    Updates the docs website after a change to the SDK or CLI. An agent skill from tetherto/qvac.

    674 GitHub stars~11k tokensUpdated today
    Auto-check passed
  • Qv Agent Stack Sync

    tetherto/qvac

    Plan and prepare the QVAC agent-stack release cascade across @qvac/inference, @qvac/sdk, @qvac/cli, @qvac/ai-sdk-provider, @qvac/opencode-plugin, and @qvac/openclaw-plugin.

    674 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Run the deterministic code-quality audit, turn related findings into contextual remediation groups, prepare approval-gated Asana proposals, reconcile recurring runs, or configure twice-monthly…

    674 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Review C++ changes for string parameter and call-site efficiency conventions (std::stringview, std::string&&, const std::string&, const char, and TransparentStringMap lookup).

    674 GitHub stars~702 tokensUpdated today
    Auto-check passed
  • Qv Addon Changelog

    tetherto/qvac

    Generate changelog entries for a target add-on package. An agent skill from tetherto/qvac.

    674 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Questions about Commit Trace

What does Commit Trace do?

Trace a commit to its published npm versions, including transitive SDK resolution with time-aware accuracy. Commit Trace is an agent skill from tetherto/qvac.

When should I use Commit Trace?

Commit Trace fits situations like: AI & LLM Engineering work in your project.

How do I install Commit Trace in Claude Code?

Run `npx skills add tetherto/qvac --skill commit-trace -a claude-code`. Or copy the skill folder (packages/ocr-ggml/.agent/skills/commit-trace in tetherto/qvac) into .claude/skills/commit-trace in your project. Claude Code loads it when a task matches its description.

How do I install Commit Trace in Codex?

Run `npx skills add tetherto/qvac --skill commit-trace -a codex`. Or copy the skill folder (packages/ocr-ggml/.agent/skills/commit-trace in tetherto/qvac) into .agents/skills/commit-trace in your project. Codex loads it when a task matches its description.

Can I use Commit Trace in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tetherto/qvac --skill commit-trace -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/commit-trace, .gemini/skills/commit-trace, .github/skills/commit-trace and .opencode/skills/commit-trace in your project.

What does Commit Trace need to run?

Going by SKILL.md and its folder, Commit Trace needs the command-line tools its instructions call (git and npm). Our summary lists: Node.js.

Does Commit Trace access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Commit Trace safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Commit Trace use?

Commit Trace is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Commit Trace use?

About 1.7k tokens (SKILL.md is roughly 6.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Commit Trace?

Skills that share tags, products or a category with Commit Trace: Helmor Bump Vendors (dohooo/helmor, 1.3k stars), Aider Delegate (amElnagdy/delegate-skills, 2.3k stars), Hugging Face LLM Trainer (huggingface/skills, 11k stars) and Compromise NLP for JavaScript (spencermountain/compromise, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Commit Trace?

tetherto (a GitHub organization) maintains it in tetherto/qvac, which has 674 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.

Source: tetherto/qvac on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.