git.update_references

A guide for finding references in several Git repositories to files moved, renamed, or deleted in the current repository. Git is a system for tracking changes to code and other files.

In plain words
What is it for?
Use it after moving, renaming, updating, or deleting files to search selected Git-controlled repositories while excluding subrepositories and symlinks.
Why use it?
Changing file locations can leave imports, paths, or other links pointing to files that no longer exist. This helps locate those references across related repositories.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/causify-ai/helpers/git.update_references
Any agent
npx skills add causify-ai/helpers --skill git.update_references
Clone the repo
git clone --depth 1 https://github.com/causify-ai/helpers

Made for: Claude Code, Codex.

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 541 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.00541
Opus 5 $0.00012 $0.00270
Sonnet 5 $0.00005 $0.00108
Haiku 4.5 $0.00002 $0.00054

Measured 2d ago against content hash 0139e7ab704c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git.update_references scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/git.update_references/SKILL.md · 62 lines

What it actually says

Step 1

  • Find all the files moved, renamed, updated, or deleted in the current repo using a command line

    > invoke git_files --branch --only-print-files
    
  • Print all the file that are moved, renamed, or deleted

    • Print the main functions changed

Step 2

  • For each file <FILE>, look for all the references to <FILE> in the repos

    • helper: the current repo
    • umd_classes: located at ~/src/umd_classes1
    • csfy: located at ~/src/csfy1
    • orange: located at ~/src/orange1
    • lemonade: located at ~/src/lemonade1
  • You must

    • Ignore searching in any Git sub repository of each repo (e.g., helpers_root)
    • Only search in files that are under Git control
    • Ignore searching in symlinks (e.g., .claude) using an approach like:
    search_repo() {
      local repo_path=$1
      local search_term=$2
    
      (cd "$repo_path" && {
        # Get submodule paths to exclude
        submodules=$(git config --file .gitmodules --name-only --get-regexp path 2>/dev/null | sed 's/.*path=//' | tr '\n' '|' | sed 's/|$//')
    
        if [ -n "$submodules" ]; then
          git ls-files | grep -v "^($submodules)" | while read -r file; do
            [ ! -L "$file" ] && echo "$file"
          done | xargs grep "$search_term" 2>/dev/null
        else
          git ls-files | while read -r file; do
            [ ! -L "$file" ] && echo "$file"
          done | xargs grep "$search_term" 2>/dev/null
        fi
      })
    }
    
  • Print the references in a table organized by

    • Repos
    • Files
  • Create a vim quickfile cfile for the locations using the conventions in @.claude/skills/cfile.rules.md

  • Pause and ask the user to continue

Step 3

  • Update the references in all the repos
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 62 lines · 24 tokens per session scan A 0139e7ab704c

Subscribe to this mod's changes

git.update_references is a skill published in the GitHub repository causify-ai/helpers (145 stars, last pushed 2d ago), licensed Apache-2.0. It adds 24 tokens to every session and 541 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens