gitnexus-impact-analysis by abhigyanpatwari/gitnexus
npx skills add https://github.com/abhigyanpatwari/gitnexus --skill gitnexus-impact-analysis1. gitnexus_impact({target: "X", direction: "upstream"}) → 哪些部分依赖于此
2. READ gitnexus://repo/{name}/processes → 检查受影响的执行流程
3. gitnexus_detect_changes() → 将当前的 git 变更映射到受影响的流程
4. 评估风险并向用户报告
如果出现"索引已过时" → 请在终端运行
npx gitnexus analyze。
- [ ] 使用 gitnexus_impact({target, direction: "upstream"}) 查找依赖项
- [ ] 首先审查 d=1 的项目(这些 **会** 被破坏)
- [ ] 检查高置信度 (>0.8) 的依赖关系
- [ ] READ processes 以检查受影响的执行流程
- [ ] 使用 gitnexus_detect_changes() 进行提交前检查
- [ ] 评估风险等级并向用户报告
| 深度 |
|---|
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 风险等级 |
|---|
| 含义 |
|---|
| d=1 | 会破坏 | 直接调用者/导入者 |
| d=2 | 可能受影响 | 间接依赖项 |
| d=3 | 可能需要测试 | 传递性影响 |
| 受影响项 | 风险 |
|---|---|
| <5 个符号,少数流程 | 低 |
| 5-15 个符号,2-5 个流程 | 中 |
15 个符号或许多流程 | 高
关键路径(认证、支付) | 严重
gitnexus_impact — 用于分析符号影响范围的主要工具:
gitnexus_impact({
target: "validateUser",
direction: "upstream",
minConfidence: 0.8,
maxDepth: 3
})
→ d=1 (会破坏):
- loginHandler (src/auth/login.ts:42) [CALLS, 100%]
- apiMiddleware (src/api/middleware.ts:15) [CALLS, 100%]
→ d=2 (可能受影响):
- authRouter (src/routes/auth.ts:22) [CALLS, 95%]
gitnexus_detect_changes — 基于 git-diff 的影响分析:
gitnexus_detect_changes({scope: "staged"})
→ 已更改: 3 个文件中的 5 个符号
→ 受影响: LoginFlow, TokenRefresh, APIMiddlewarePipeline
→ 风险: 中
1. gitnexus_impact({target: "validateUser", direction: "upstream"})
→ d=1: loginHandler, apiMiddleware (会破坏)
→ d=2: authRouter, sessionManager (可能受影响)
2. READ gitnexus://repo/my-app/processes
→ LoginFlow 和 TokenRefresh 涉及 validateUser
3. 风险: 2 个直接调用者,2 个流程 = 中
每周安装量
52
代码仓库
GitHub 星标数
11.8K
首次出现
2026年2月25日
安全审计
安装于
github-copilot51
codex51
amp51
kimi-cli51
gemini-cli51
cursor51
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 analyzein terminal.
- [ ] 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
| Depth | Risk Level | Meaning |
|---|---|---|
| d=1 | WILL BREAK | Direct callers/importers |
| d=2 | LIKELY AFFECTED | Indirect dependencies |
| d=3 | MAY NEED TESTING | Transitive effects |
| 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
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
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
Weekly Installs
52
Repository
GitHub Stars
11.8K
First Seen
Feb 25, 2026
Security Audits
Gen Agent Trust HubWarnSocketPassSnykWarn
Installed on
github-copilot51
codex51
amp51
kimi-cli51
gemini-cli51
cursor51
CodeQL代码扫描配置指南 - GitHub Actions工作流与CLI本地运行教程
632 周安装