Official agent skill

Gitnexus Impact Analysis

by aws-samples in aws-samples/sample-kolya-br-proxy

A skill your agent uses when the user wants to know what will break if they change something, or needs safety analysis before editing code.

OfficialMIT-0Auto-check passed

Install Gitnexus Impact Analysis

skills CLI

$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a claude-code

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

GitHub CLI

$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-impact-analysis --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/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-impact-analysis .claude/skills/gitnexus-impact-analysis && 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/

Paste into Claude Code

Install the "gitnexus-impact-analysis" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis into .claude/skills/gitnexus-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-impact-analysis", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-impact-analysis --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-impact-analysis .agents/skills/gitnexus-impact-analysis && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "gitnexus-impact-analysis" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis into .agents/skills/gitnexus-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-impact-analysis", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-impact-analysis --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-impact-analysis .cursor/skills/gitnexus-impact-analysis && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "gitnexus-impact-analysis" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis into .cursor/skills/gitnexus-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-impact-analysis", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/aws-samples/sample-kolya-br-proxy.git --path .claude/skills/gitnexus/gitnexus-impact-analysis

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-impact-analysis --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-impact-analysis .gemini/skills/gitnexus-impact-analysis && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "gitnexus-impact-analysis" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis into .gemini/skills/gitnexus-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-impact-analysis", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-impact-analysis

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-impact-analysis .github/skills/gitnexus-impact-analysis && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "gitnexus-impact-analysis" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis into .github/skills/gitnexus-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-impact-analysis", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install aws-samples/sample-kolya-br-proxy gitnexus-impact-analysis --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/aws-samples/sample-kolya-br-proxy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/gitnexus/gitnexus-impact-analysis .opencode/skills/gitnexus-impact-analysis && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "gitnexus-impact-analysis" agent skill from https://github.com/aws-samples/sample-kolya-br-proxy/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis into .opencode/skills/gitnexus-impact-analysis/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "gitnexus-impact-analysis", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: gitnexus-impact-analysis
GitHub stars: 106
Used in: 11 other repos
Token cost: ~723 tokens
SKILL.md length: 123 words
Files: 1
Skills in repo: 6
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT-0

At a glance

A skill your agent uses when the user wants to know what will break if they change something, or needs safety analysis before editing code.

The user wants to know what will break if they change something
SKILL.md covers When to Use, Workflow, Checklist and Understanding Output, plus 3 more sections
Calls npx
Needs safety analysis before editing code

What it does

Gitnexus Impact Analysis is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

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

The licence is MIT-0.

When your agent uses it

The user wants to know what will break if they change something
Needs safety analysis before editing code

Example prompts

“Is it safe to change X?”
“What depends on this?”
“What will break?”
“/gitnexus-impact-analysis”

Requirements

Node.js

What it can do on your machine

Read from SKILL.md and the folder at commit 9c3dcee. 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:
- npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npx, 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

Gitnexus Impact Analysis loads about 723 tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 123 words of instructions outside code blocks.

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

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 aws-samples/sample-kolya-br-proxy at commit 9c3dcee, republished under its MIT-0 licence (© aws-samples). 123 words, ~723 tokens.

Download SKILL.mdSave it as .claude/skills/gitnexus-impact-analysis/SKILL.md (or your agent's skills folder).

name: gitnexus-impact-analysis
description: Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"

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 "Index is stale" → run npx gitnexus analyze in terminal.

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

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

Risk Assessment

Affected	Risk
<5 symbols, few processes	LOW
5-15 symbols, 2-5 processes	MEDIUM
>15 symbols or many processes	HIGH
Critical path (auth, payments)	CRITICAL

Tools

gitnexus_impact — the primary tool for symbol blast radius:

gitnexus_impact({
  target: "validateUser",
  direction: "upstream",
  minConfidence: 0.8,
  maxDepth: 3
})

→ d=1 (WILL BREAK):
  - loginHandler (src/auth/login.ts:42) [CALLS, 100%]
  - apiMiddleware (src/api/middleware.ts:15) [CALLS, 100%]

→ d=2 (LIKELY AFFECTED):
  - authRouter (src/routes/auth.ts:22) [CALLS, 95%]

gitnexus_detect_changes — git-diff based impact analysis:

gitnexus_detect_changes({scope: "staged"})

→ Changed: 5 symbols in 3 files
→ Affected: LoginFlow, TokenRefresh, APIMiddlewarePipeline
→ Risk: MEDIUM

Example: "What breaks if I change validateUser?"

1. gitnexus_impact({target: "validateUser", direction: "upstream"})
   → d=1: loginHandler, apiMiddleware (WILL BREAK)
   → d=2: authRouter, sessionManager (LIKELY AFFECTED)

2. READ gitnexus://repo/my-app/processes
   → LoginFlow and TokenRefresh touch validateUser

3. Risk: 2 direct callers, 2 processes = MEDIUM

Files

Just SKILL.md in .claude/skills/gitnexus/gitnexus-impact-analysis of aws-samples/sample-kolya-br-proxy.

Open the folder on GitHubat commit 9c3dcee

Used in 12 other repositories

We found 14 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 11 other GitHub owners. This page covers the copy in aws-samples/sample-kolya-br-proxy, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Gitnexus Impact Analysis 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.

Gitnexus Impact Analysis compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Gitnexus Impact Analysis this skillaws-samples/sample-kolya-br-proxy	106	11 repos	~723	Automated safety check: Pass	MIT-0	yesterday
V5 Breaking Changesremotion-dev/remotion	62k	—	~879	Automated safety check: Pass	Custom licence	today
What Breakssuboss87/FDEOps	953	—	~337	Automated safety check: Pass	MIT	yesterday
Performing Privacy Impact Assessmentmukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.6k	Automated safety check: Pass	Apache-2.0	1 mo ago
BreakJDArmy/BREAK	385	—	~2.2k	Automated safety check: Notes	Apache-2.0	8 days ago
Datalineage Bigquery Asset Impact Analysisgoogle/skills	21k	—	~1.7k	Automated safety check: Pass	Apache-2.0	today

Similar skills

V5 Breaking Changes
remotion-dev/remotion
Official
Implement or review a Remotion 5 breaking change while the v4 and v5 release lines still share code.
62k GitHub stars~879 tokensUpdated today
Media & CreativeAuto-check passed
What Breaks
suboss87/FDEOps
Assess the impact of a proposed change on dependencies and shared infrastructure.
953 GitHub stars~337 tokensUpdated yesterday
Auto-check passed
Performing Privacy Impact Assessment
mukul975/Anthropic-Cybersecurity-Skills
Automates the Privacy Impact Assessment (PIA) workflow including data flow mapping, privacy risk scoring matrices, GDPR Article 35 DPIA and CCPA/CPRA alignment checks, data inventory cataloging, and…
34k GitHub stars~2.6k tokensUpdated 1 mo ago
Legal & ComplianceAuto-check passed
Break
JDArmy/BREAK
BREAK 业务风险枚举与规避知识库 — 查询业务安全风险、规避手段、攻击工具、威胁行为者、行业术语和典型案例，或基于知识库回答业务安全问题
385 GitHub stars~2.2k tokensUpdated 8 days ago
Auto-check: notes
Datalineage Bigquery Asset Impact Analysis
google/skills
Official
Analyzes the downstream impact (blast radius) when a BigQuery table or view is broken, stale, or modified.
21k GitHub stars~1.7k tokensUpdated today
DatabasesAuto-check passed
Breaking Change Analysis
ruby-git/ruby-git
Assesses what an API change would break before it is made, finds every usage, documents the impact and plans a deprecation or migration path.
1.8k GitHub stars~1.7k tokensUpdated 5 days ago
DevelopmentAuto-check passed

Questions about Gitnexus Impact Analysis

What does Gitnexus Impact Analysis do?

A skill your agent uses when the user wants to know what will break if they change something, or needs safety analysis before editing code. Gitnexus Impact Analysis is an agent skill from aws-samples/sample-kolya-br-proxy, published by the product's own GitHub organization. Use when the user wants to know what will break if they change something, or needs safety analysis before editing code.

When should I use Gitnexus Impact Analysis?

Gitnexus Impact Analysis fits situations like: the user wants to know what will break if they change something; needs safety analysis before editing code.

How do I install Gitnexus Impact Analysis in Claude Code?

Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a claude-code`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-impact-analysis in aws-samples/sample-kolya-br-proxy) into .claude/skills/gitnexus-impact-analysis in your project. Claude Code loads it when a task matches its description.

How do I install Gitnexus Impact Analysis in Codex?

Run `npx skills add aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a codex`. Or copy the skill folder (.claude/skills/gitnexus/gitnexus-impact-analysis in aws-samples/sample-kolya-br-proxy) into .agents/skills/gitnexus-impact-analysis in your project. Codex loads it when a task matches its description.

Can I use Gitnexus Impact Analysis 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 aws-samples/sample-kolya-br-proxy --skill gitnexus-impact-analysis -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gitnexus-impact-analysis, .gemini/skills/gitnexus-impact-analysis, .github/skills/gitnexus-impact-analysis and .opencode/skills/gitnexus-impact-analysis in your project.

What does Gitnexus Impact Analysis need to run?

Going by SKILL.md and its folder, Gitnexus Impact Analysis needs the command-line tools its instructions call (npx). Our summary lists: Node.js.

Does Gitnexus Impact Analysis access the network?

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

Is Gitnexus Impact Analysis 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 Gitnexus Impact Analysis use?

Gitnexus Impact Analysis is published under the MIT-0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gitnexus Impact Analysis use?

About 723 tokens (SKILL.md is roughly 2.9k 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 Gitnexus Impact Analysis?

Skills that share tags, products or a category with Gitnexus Impact Analysis: V5 Breaking Changes (remotion-dev/remotion, 62k stars), What Breaks (suboss87/FDEOps, 953 stars), Performing Privacy Impact Assessment (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Break (JDArmy/BREAK, 385 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gitnexus Impact Analysis?

aws-samples (a GitHub organization, an official publisher) maintains it in aws-samples/sample-kolya-br-proxy, which has 106 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 5, 2026.

Source: aws-samples/sample-kolya-br-proxy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Gitnexus Impact Analysis

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Impact Analysis with GitNexus

When to Use

Workflow

Checklist

Understanding Output

Risk Assessment

Tools

Example: "What breaks if I change validateUser?"

Files

Used in 12 other repositories

Compare with similar skills

Similar skills

More from aws-samples/sample-kolya-br-proxy

Questions about Gitnexus Impact Analysis