version-sentinel
/version-sentinel
Use when adding, bumping, or changing a dependency in package.json, requirements*.txt, constraints*.txt, pyproject.toml, Cargo.toml, *.csproj, *.fsproj, or *.vbproj. Triggered automatically by version-sentinel's PreToolUse hook (where the host supports hooks) — this skill explains how to satisfy the block and record a version check.
- Author
- ksegit ↗
- Repository
- version-sentinel ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when adding, bumping, or changing a dependency in package.json, requirements*.txt, constraints*.txt, pyproject.toml, Cargo.toml, *.csproj, *.fsproj, or *.vbproj. Triggered automatically by version-sentinel's PreToolUse hook (where the host supports hooks) — this skill explains how to satisfy the block and record a version check.
Original author description
Use when adding, bumping, or changing a dependency in package.json, requirements*.txt, constraints*.txt, pyproject.toml, Cargo.toml, *.csproj, *.fsproj, or *.vbproj. Triggered automatically by version-sentinel's PreToolUse hook (where the host supports hooks) — this skill explains how to satisfy the block and record a version check.
How it works
- When you see a BLOCKED message
- Intentional non-latest pins
- What NOT to do
- Audit command
SKILL.md preview
---
name: version-sentinel
description: Use when adding, bumping, or changing a dependency in package.json, requirements*.txt, constraints*.txt, pyproject.toml, Cargo.toml, *.csproj, *.fsproj, or *.vbproj. Triggered automatically by version-sentinel's PreToolUse hook (where the host supports hooks) — this skill explains how to satisfy the block and record a version check.
---
# Version Sentinel — Workflow
The `version-sentinel` setup blocks dependency changes until you've verified the package version against its upstream registry. Here's the required flow. (On hosts without hook support, such as Zed, this same flow applies manually — follow it whenever you touch a manifest or run an install command.)
## When you see a BLOCKED message
If a tool call exits 2 with `BLOCKED: version-sentinel`, you must:
1. **Look up the latest version.** Use a web search first:
- `npm`: search `"<pkg> latest version site:npmjs.com"`
- `pip`/`pyproject`: search `"<pkg> latest version site:pypi.org"`
- `csproj`: search `"<pkg> latest version site:nuget.org"`
- `cargo`: search `"<pkg> latest version site:crates.io"`
If web search is unavailable, fetch the registry URL directly, or consult a docs tool (e.g. context7) for the package.
2. **Record the check.** Run in the terminal:
bash scripts/vs-record.sh <ecosystem> <pkg> <version-you-intend-to-install> <source-url>
The source must be an `http(s)://` URL from your search OR prefixed with `intentional:` for deliberate pins.
3. **Retry with the verified version.** If the blocked input omitted the version or used a floating tag such as `latest`, rewrite it first. For example, use `npm install lodash@4.17.21`, not `npm install lodash` or `npm install lodash@latest`.
Local paths, URLs, git sources, and workspace dependencies are outside registry-version checks. A NuGet `PackageReference` without `Version` may use Central Package Management, so the manifest gate ignores that form.
## Intentional non-latest pins
If you genuinely intend to install an older version (CVE mitigation, compat, private registry), record with:
bash scripts/vs-record.sh <ecosystem> <pkg> <version> "intentional: <brief reason>"
This passes the hook and is flagged as `intentional-pin` (not `DRIFT`) in `bash scripts/check-versions.sh` output.
## What NOT to do
- Don't fake a source URL you didn't actually see. The skill contract assumes honest reporting.
- Don't try to bypass the hook with `git commit --no-verify` or similar — the hook runs on file edits and terminal commands, not on git.
- Don't `unset VS_DISABLE` without the user's awareness; that's an escape hatch for throwaway sessions, not normal flow.
## Audit command
`bash scripts/check-versions.sh` scans manifests within 4 directory levels of the current directory and reports drift. Run it before tagging a release.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ksegit/version-sentinel | 100 | MIT |
| ksegit/version-sentinel | 100 | MIT |
Database snapshot: 13.11.2026 · package version 2dde9466eae6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100evaluate-dependency
Use when adding or evaluating a project dependency in any language, phrases like "should I use X library", "evaluate <package>", "what library for Y", or when reviewing a PR that touches a manifest (go.mod, package.json, requirements.txt, pyproject.toml, Cargo.toml, Gemfile,… - 100python-best-practices
Use when reading or writing Python files (.py, pyproject.toml, requirements.txt). - 100scan-before-add
Use when selecting, comparing, or recommending third-party libraries, and before adding a new dependency (go.mod, package.json, pyproject.toml, requirements.txt, Cargo.toml, pom.xml, *.csproj, Gemfile, composer.json). Applies both when you choose the candidates and when the user… - 100bump-version
Bump the membrowse package version (pyproject.toml and the Claude plugin manifests), open a PR, wait for CI to pass and squash-merge it. Use when the user asks to bump the version, cut a patch/minor/major release version, or run /bump-version. Accepts an optional argument -… - 100managing-cargo-dependencies
Cargo.toml dependency management patterns for HASH workspace. Use when adding, updating, or removing dependencies, organizing Cargo.toml sections, configuring version pinning and default features, or managing public dependencies. - 90python-tooling
Configure Python tooling, dependency surfaces, static analysis, and verification gates. Use when editing `pyproject.toml`, `requirements.txt`, `pytest.ini`, `ruff`, `pyright`, CI, or Python release checks.