dhpk-gitnexus-impact-analysis

dhpk-gitnexus-impact-analysis is a skill for Claude Code, Codex from hmj1026/dhpk. It costs 110 tokens per session (1,110 once invoked), scanned A, original, MIT.

A code-change impact checker that uses GitNexus, a map of relationships in a codebase, to find what depends on a symbol or file.

In plain words
What is it for?
Use it to find callers and dependent code, check which application flows may be affected, and assess the risk of pending changes.
Why use it?
It shows the likely blast radius before you edit or commit, so you can spot affected code and execution paths instead of relying on guesswork.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Part of the dhpk plugin — 65 skills, 31 commands, 37 agents, 4 hooks shipped together

Good fit Use it to find callers and dependent code, check which application flows may be affected, and assess the risk of pending changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hmj1026/dhpk/dhpk-gitnexus-impact-analysis
View source ↗ hmj1026/dhpk
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.

Any agent
npx skills add hmj1026/dhpk --skill dhpk-gitnexus-impact-analysis
Clone the repo
git clone --depth 1 https://github.com/hmj1026/dhpk

Made for: Claude Code, Codex.

Or install dhpk, the plugin that ships this one along with the rest of its 65 skills, 31 commands, 37 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for dhpk-gitnexus-impact-analysis

README.md
[![agentmods](https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-gitnexus-impact-analysis/github.svg)](https://agentmods.dev/skills/hmj1026/dhpk/dhpk-gitnexus-impact-analysis)
Your own site
<a href="https://agentmods.dev/skills/hmj1026/dhpk/dhpk-gitnexus-impact-analysis"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-gitnexus-impact-analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for dhpk-gitnexus-impact-analysis

Your own site · 80×15
<a href="https://agentmods.dev/skills/hmj1026/dhpk/dhpk-gitnexus-impact-analysis"><img src="https://agentmods.dev/badge/skills/hmj1026/dhpk/dhpk-gitnexus-impact-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,110 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00110 $0.01110
Opus 5 $0.00055 $0.00555
Sonnet 5 $0.00022 $0.00222
Haiku 4.5 $0.00011 $0.00111

Measured 5d ago against content hash c3869106e3a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

dhpk-gitnexus-impact-analysis 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 5d 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.

generated/claude-profiles/compat-v1/package/skills/dhpk-gitnexus-impact-analysis/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Impact Analysis with GitNexus

When to Use

  • "Is it safe to change this function?"
  • "What will break if I modify X?"
  • "Show me the blast radius"
  • "Who uses this code?"
  • Before making non-trivial code changes
  • Before committing — to understand what your changes affect

Workflow

1. gitnexus_impact({target: "X", direction: "upstream"})  → What depends on this
2. READ gitnexus://repo/{name}/processes                   → Check affected execution flows
3. gitnexus_detect_changes()                               → Map current git changes to affected flows
4. Assess risk and report to user

If the context reports a stale index, follow dhpk-gitnexus-guide for the single stale-index recovery path before continuing this workflow.

Checklist

- [ ] gitnexus_impact({target, direction: "upstream"}) to find dependents
- [ ] Review d=1 items first (these WILL BREAK)
- [ ] Check high-confidence (>0.8) dependencies
- [ ] READ processes to check affected execution flows
- [ ] gitnexus_detect_changes() for pre-commit check
- [ ] Assess risk level and report to user

Output

Return a compact report containing the target symbol, index freshness, direct callers, affected execution flows, risk level, and next verification commands. Mark graph gaps, dynamic references, and external consumers as uncertainties instead of treating the graph as exhaustive.

Verification

  • The target and direction used for gitnexus_impact are recorded.
  • Direct dependents are separated from indirect dependents.
  • Affected process resources were checked, not inferred from callers only.
  • HIGH or CRITICAL risk is surfaced before any edit proceeds.
  • gitnexus_detect_changes is run before commit when the task changes code.

The schema, tool names, resource catalog, and stale-index recovery are owned by dhpk-gitnexus-guide; this skill owns blast-radius sequencing and risk output.

Understanding Output

Depth Risk Level Meaning
d=1 WILL BREAK Direct callers/importers
d=2 LIKELY AFFECTED Indirect dependencies
d=3 MAY NEED TESTING Transitive effects

Read the full file on GitHub · 125 lines

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. 5d ago First seen · 125 lines · 110 tokens per session scan A c3869106e3a4

Subscribe to this mod's changes

dhpk-gitnexus-impact-analysis is a skill published in the GitHub repository hmj1026/dhpk (2 stars, last pushed today), licensed MIT. It adds 110 tokens to every session and 1,110 once invoked, about $0.0006 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-09-05.

Related

Other skills, from other repositories

pr

Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.

umputun/cc-thingz · 51 tokens

release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…

hyhmrright/brooks-lint · 135 tokens

pr-threads-address

Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.

posit-dev/skills · 48 tokens

procoder

Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…

azrtydxb/procoder · 101 tokens

OCR Review-to-Approval Loop

Drive a PR to an approved code review by looping OCR's multi-agent review and address steps. Runs /ocr:review then /ocr:address repeatedly until the review verdict is APPROVE, then one final /ocr:address for leftover suggestions, posting every review and every address round to the GitHub PR as comments. Use when the…

spencermarx/open-code-review · 178 tokens

review-pr

Autonomous PR review that posts high-signal, human-voiced comments under your account. Use when reviewing someone else's PR or your own manifest-driven PR, when you want a precision-tuned review you can walk away from, or when the user asks to review a PR, post a PR review, autoreview, loop review, or watch a PR.

doodledood/manifest-dev · 75 tokens