Agent skill

Anchor Vet

by lynxlangya in lynxlangya/techne

Evidence-gated diff review for PRs, branches, commit ranges, staged code changes, and merge readiness checks.

MITAuto-check passedDevelopment

Install Anchor Vet

skills CLI
$ npx skills add lynxlangya/techne --skill anchor-vet -a claude-code

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

GitHub CLI
$ gh skill install lynxlangya/techne anchor-vet --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/lynxlangya/techne.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/anchor-vet .claude/skills/anchor-vet && 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
anchor-vet
GitHub stars
105
Token cost
~1.3k tokens
SKILL.md length
534 words
Files
6 (incl. scripts)
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Evidence-gated diff review for PRs, branches, commit ranges, staged code changes, and merge readiness checks.

  • Works in 8 steps: Anchor the scope. Check out the reviewed… → Read every hunk. Inspect the full diff… → Walk the blast radius. For each… → …
  • An AI reviewer must review a concrete git-anchored diff
  • SKILL.md covers Trigger Check, Forced Procedure, Script Contract and Stop Conditions
  • Runs Python scripts from its folder; calls python3

What it does

Anchor Vet is an agent skill from lynxlangya/techne. Evidence-gated diff review for PRs, branches, commit ranges, staged code changes, and merge readiness checks. Use when an AI reviewer must review a concrete git-anchored diff, judge whether code is safe to merge, inspect a PR URL or branch, cross-examine PR or commit claims, account blast radius, or render approve/request-changes/blocked verdicts. Do not use for design-only review, whole-codebase audits, bug fixing, or code authoring without a git diff under judgment.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `README-CN.md`, `README.md` and `eval.md`).

It sits in Development, covering Debugging and Git workflow. It works with Git. The repository describes itself as: Forcing-function skills for AI agents — validated to improve behavior, not just change it. The licence is MIT.

When your agent uses it

  • An AI reviewer must review a concrete git-anchored diff
  • Judge whether code is safe to merge
  • Inspect a PR URL
  • Cross-examine PR

Example prompts

  • “/anchor-vet”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Anchor the scope. Check out the reviewed head locally. Capture external
  2. Read every hunk. Inspect the full diff and every hunk in scope.json.
  3. Walk the blast radius. For each candidate symbol, read the references
  4. Account weak or symbolless hunks. For weak/symbolless hunks, use a
  5. Cross-examine claims. Disposition every anchored claim id from
  6. Hunt findings with severity honesty. Use only blocking, concern, and
  7. Write and check review.json. Run
  8. Render the verdict through the gate. Run

What it can do on your machine

Read from SKILL.md and the folder at commit 56bbe71. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

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

  • Network

    No URLs in SKILL.md.

    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

Anchor Vet loads about 1.3k tokens when it runs. Until then it costs about 121 tokens; SKILL.md has 534 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from lynxlangya/techne at commit 56bbe71, republished under its MIT licence (© lynxlangya). 534 words, ~1,275 tokens.

Download SKILL.mdSave it as .claude/skills/anchor-vet/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
anchor-vet
description
Evidence-gated diff review for PRs, branches, commit ranges, staged code changes, and merge readiness checks. Use when an AI reviewer must review a concrete git-anchored diff, judge whether code is safe to merge, inspect a PR URL or branch, cross-examine PR or commit claims, account blast radius, or render approve/request-changes/blocked verdicts. Do not use for design-only review, whole-codebase audits, bug fixing, or code authoring without a git diff under judgment.

anchor-vet

Force the skipped move in code review: prove the reviewed diff's scope, blast radius, claims, findings, and verdict are anchored to git evidence.

Trigger Check

Use this skill only when there is a concrete code change to judge: a PR, branch, commit range, or staged review target.

Boundary test: can you name a base...head pair of git states whose difference is the artifact under judgment? If yes, use anchor-vet. If no, get the branch or ref first; do not review pasted diffs or prose descriptions.

Do not use anchor-vet for design feedback without a diff, whole-codebase audits, feature implementation, bug fixing, formatting-only tasks, or document review. If the user asks you to fix findings too, render the review verdict first; fixes are a separate task, and behavioral fixes route to anchor-repro.

Forced Procedure

  1. Anchor the scope. Check out the reviewed head locally. Capture external claims before init: for PRs, save the title/body from gh pr view --json title,body --jq '.title + "\n\n" + (.body // "")' to a claims file. Run: python3 skills/anchor-vet/scripts/vet_gate.py init --project <root> --review <slug> --base <ref> --head <ref> --claims-file <path> or, only when there are genuinely no external claims, --no-claims.
  2. Read every hunk. Inspect the full diff and every hunk in scope.json. If the diff is too large to read honestly, stop and propose a split.
  3. Walk the blast radius. For each candidate symbol, read the references found by the gate. Record examined refs with effect and a one-line note. Examined means you opened/read the reference and judged how the change affects it.
  4. Account weak or symbolless hunks. For weak/symbolless hunks, use a verified enclosingUnit when a named unit exists, or file-level with a reason only for genuinely unit-less code/config/prose.
  5. Cross-examine claims. Disposition every anchored claim id from scope.json: verified, contradicted, not-verifiable-from-diff, or non-claim. Verified/contradicted claims need citations.
  6. Hunt findings with severity honesty. Use only blocking, concern, and nit. Cite findings. A blocking finding needs R2 cited evidence or an R3 repro probe. When a behavioral assertion is cheap to demonstrate, record a failing anchor-repro ledger entry against the reviewed head and cite it with entrySha256.
  7. Write and check review.json. Run: python3 skills/anchor-vet/scripts/vet_gate.py check --project <root> --review <slug>. Fix check failures by doing the missing review work, not by padding JSON.
  8. Render the verdict through the gate. Run: python3 skills/anchor-vet/scripts/vet_gate.py close --project <root> --review <slug> --verdict approve|request-changes|blocked. Report the verdict, cite verdict.json, and name each finding's evidence rung.
Show full SKILL.md (127 more words)Show less

Script Contract

Artifacts are written under the target project:

text
.techne/review/<slug>/
  scope.json    # computed by init
  review.json   # authored by the reviewer
  report.json   # computed by check
  verdict.json  # computed by close

Generated .techne/ output belongs to target projects. Do not commit it to this repository.

Review skeleton:

json
{
  "schema": "techne.vet/1",
  "symbols": [
    {
      "id": "s-...",
      "symbol": "changedName",
      "disposition": "reviewed",
      "refs": [
        {
          "file": "src/caller.py",
          "line": 42,
          "effect": "unaffected",
          "note": "caller passes the same contract"
        }
      ]
    }
  ],
  "hunks": [],
  "claims": [
    {
      "ids": ["c-..."],
      "disposition": "verified",
      "citations": [{"file": "src/change.py", "line": 10}]
    }
  ],
  "findings": [],
  "testsAcknowledgment": "No tests changed; the diff is docs-only or existing coverage is enough because ..."
}

Use reference.md for the full JSON schema, rubrics, exclusions, weak spots, and probe guidance.

Stop Conditions

  • Stop if no git-anchored base...head diff is available.
  • Stop if init refuses because of dirty worktree, missing merge base, or head mismatch; fix the setup or record blocked.
  • Stop if the review is too large to read in full; propose a split instead of sampling silently.
  • Stop before approve if refs, hunks, claims, or test acknowledgment remain unaccounted.
  • If head moves mid-review, do not fight the tool. Close the old slug as blocked --reason ... or leave it, then start a new slug for the new head.

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

Files

SKILL.md and 5 other files (scripts) in skills/anchor-vet of lynxlangya/techne.

  • SKILL.md
  • README-CN.md
  • README.md
  • eval.md
  • reference.md
  • scripts/vet_gate.py

Open the folder on GitHubat commit 56bbe71

Compare with similar skills

Anchor Vet 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.

Anchor Vet compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Anchor Vet this skilllynxlangya/techne105—~1.3kAutomated safety check: PassMIT
Git History Bug Auditben-manes/caffeine18k—~3.3kAutomated safety check: PassApache-2.0
Stax Devcesarferreira/stax130—~987Automated safety check: PassMIT
Crankpigweed-project/pigweed548—~2.1kAutomated safety check: PassApache-2.0
Build Deploy TroubleshootParesh-Maheshwari/morphe-ai178—~1.1kAutomated safety check: PassGPL-3.0
Targeted Emergency Bug FixVeryGoodOpenSource/vgv-wingspan109—~1.9kAutomated safety check: PassMIT

Similar skills

  • Git History Bug Audit

    ben-manes/caffeine

    Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.

    18k GitHub stars~3.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Stax Dev

    cesarferreira/stax

    Development harness for the stax Rust CLI project. An agent skill from cesarferreira/stax.

    130 GitHub stars~987 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Crank

    pigweed-project/pigweed

    Autonomous "take the next step" workflow orchestrator for Pigweed.

    548 GitHub stars~2.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Build Deploy Troubleshoot

    Paresh-Maheshwari/morphe-ai

    Build, test, deploy, and troubleshoot Morphe patches — gradle commands, CLI usage, git workflow, common errors and fixes.

    178 GitHub stars~1.1k tokensUpdated 12 days ago
    DevelopmentAuto-check passed
  • Targeted Emergency Bug Fix

    VeryGoodOpenSource/vgv-wingspan

    Applies a minimal fix to an emergency bug through triage, root-cause location, a hotfix branch and a blast-radius check, with tests and review still required.

    109 GitHub stars~1.9k tokensUpdated 4 days ago
    DevelopmentAuto-check passed
  • Trace And Isolate

    rohitg00/skillkit

    Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code.

    1.5k GitHub stars~1.8k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

More from lynxlangya/techne

  • Anchor Intake

    lynxlangya/techne

    Interrogate a written engineering implementation brief before work starts.

    105 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed
  • Anchor Repro

    lynxlangya/techne

    Reproduce a behavioral bug before fixing it, record the failing probe, and verify the fix with the same probe.

    105 GitHub stars~1.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Anchor Viz

    lynxlangya/techne

    Draw a faithful architecture or structure diagram of a real codebase or project by scanning the actual repo, never guessing.

    105 GitHub stars~1.4k tokensUpdated 3 mo ago
    Auto-check passed

Works with

Categories

Questions about Anchor Vet

What does Anchor Vet do?

Evidence-gated diff review for PRs, branches, commit ranges, staged code changes, and merge readiness checks. Anchor Vet is an agent skill from lynxlangya/techne. Evidence-gated diff review for PRs, branches, commit ranges, staged code changes, and merge readiness checks.

When should I use Anchor Vet?

Anchor Vet fits situations like: an AI reviewer must review a concrete git-anchored diff; judge whether code is safe to merge; inspect a PR URL; cross-examine PR.

How do I install Anchor Vet in Claude Code?

Run `npx skills add lynxlangya/techne --skill anchor-vet -a claude-code`. Or copy the skill folder (skills/anchor-vet in lynxlangya/techne) into .claude/skills/anchor-vet in your project. Claude Code loads it when a task matches its description.

How do I install Anchor Vet in Codex?

Run `npx skills add lynxlangya/techne --skill anchor-vet -a codex`. Or copy the skill folder (skills/anchor-vet in lynxlangya/techne) into .agents/skills/anchor-vet in your project. Codex loads it when a task matches its description.

Can I use Anchor Vet 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 lynxlangya/techne --skill anchor-vet -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/anchor-vet, .gemini/skills/anchor-vet, .github/skills/anchor-vet and .opencode/skills/anchor-vet in your project.

What does Anchor Vet need to run?

Going by SKILL.md and its folder, Anchor Vet needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Anchor Vet access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Anchor Vet 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Anchor Vet use?

Anchor Vet is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Anchor Vet use?

About 1.3k tokens (SKILL.md is roughly 5.1k 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 Anchor Vet?

Skills that share tags, products or a category with Anchor Vet: Git History Bug Audit (ben-manes/caffeine, 18k stars), Stax Dev (cesarferreira/stax, 130 stars), Crank (pigweed-project/pigweed, 548 stars) and Build Deploy Troubleshoot (Paresh-Maheshwari/morphe-ai, 178 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Anchor Vet?

lynxlangya (a GitHub user) maintains it in lynxlangya/techne, which has 105 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 2, 2026.

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