Token导航 LogoToken导航

Agent Skill · 研究检索

dependency-resolver(依赖解析器)

dependency-resolver 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

dependency-resolver 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证为 MIT,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 32,689。

总安装 2,472周安装 101GitHub Stars 55下载 847核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:dependency-resolver(依赖解析器)
来源仓库:https://github.com/rysweet/amplihack
仓库路径:skills/dependency-resolver
安装命令:
npx skills add https://github.com/rysweet/amplihack --skill dependency-resolver
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/rysweet/amplihack --skill dependency-resolver

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于检测本地与 CI 环境的依赖差异。适用于 Codex、Claude、Cursor、Gemini CLI,支持 GitHub 安装。预防因版本漂移导致的 CI 失败。在推送前拦截环境不一致问题。dependency-resolver 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

输出为环境对比报告与修复建议。

来源仓库内路径:skills/dependency-resolver

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/rysweet/amplihack --skill dependency-resolver;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

dependency-resolver 怎么安装?

在终端执行 npx skills add https://github.com/rysweet/amplihack --skill dependency-resolver。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

dependency-resolver 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

dependency-resolver 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/rysweet/amplihack --skill dependency-resolver;npx skills add rysweet/amplihack --skill "dependency-resolver" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

dependency-resolver 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

dependency-resolver 用的人多吗?

公开数据是累计安装 2,472 次,近一周安装 101 次,下载 847 次,GitHub 55 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

dependency-resolver 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
dependency-resolver

依赖解析器 · 本页

2,47255执行命令MIT通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Dependency Resolver Skill

Purpose

This skill detects and resolves local vs CI environment mismatches BEFORE push, preventing the 20-45 minute debug cycles documented in DISCOVERIES.md ("CI Failure Resolution Process Analysis" entry).

The skill addresses a critical gap: existing tools (ci-diagnostic-workflow, pre-commit-diagnostic) fix issues AFTER they occur. This skill catches mismatches BEFORE push.

Problem Statement

From DISCOVERIES.md analysis:

  • Environment mismatches (Local Python 3.12 vs CI Python 3.11) cause 20-25 min investigation overhead
  • Version drift (local ruff 0.12.7 vs CI ruff 0.13.0) causes silent failures
  • 45-minute complex debugging sessions traced to dependency conflicts
  • No automated pre-push environment comparison exists

Execution Instructions

When activated, execute these steps autonomously:

Step 1: Collect Local Environment

# Python version
python --version

# Installed tool versions
pip show ruff black pyright mypy 2>/dev/null | grep -E "^(Name|Version):"

# Pre-commit hook versions (if available)
cat .pre-commit-config.yaml 2>/dev/null | grep -E "rev:|repo:"

Step 2: Read CI Configuration

Read(file_path=".github/workflows/ci.yml")
Read(file_path="pyproject.toml")
Read(file_path=".pre-commit-config.yaml")

Extract:

  • CI Python version (look for python-version:)
  • Required tool versions from pyproject.toml
  • Pre-commit hook versions from.pre-commit-config.yaml

Step 3: Compare Environments

Build comparison table:

ComponentLocalCIStatus
Python3.12.103.11MISMATCH
ruff0.12.70.13.0MISMATCH
black24.3.024.3.0OK

Step 4: Generate Recommendations

For each mismatch, provide actionable fix:

Python Version Mismatch:

# Option A: Use pyenv to match CI version
pyenv install 3.11
pyenv local 3.11

# Option B: Update CI to match local (if local is intentional)
# Edit .github/workflows/ci.yml line 33

Tool Version Mismatch:

# Pin versions in pyproject.toml
pip install ruff==0.13.0

# Or update pre-commit hooks
pre-commit autoupdate

Step 5: Auto-Fix (When Requested)

If user requests auto-fix:

  1. Update.pre-commit-config.yaml with latest versions
  2. Run pre-commit autoupdate
  3. Regenerate requirements.txt if applicable
  4. Stage changes for commit

Integration Points

With fix-agent

Integrates with fix-agent templates for:

  • Import/dependency fixes (Template 1)
  • Configuration fixes (Template 2)
  • CI/CD fixes (Template 4)

With pre-commit-diagnostic

Hand-off when pre-commit failures detected after version sync.

With ci-diagnostic-workflow

Hand-off for post-push CI failures not caught by pre-push validation.

Common Mismatch Patterns

Pattern 1: Python Minor Version Drift

Symptoms:

  • Type errors only in CI
  • Import errors with newer syntax
  • f-string issues

Fix:

# Check CI Python version
grep -r "python-version" .github/workflows/

# Match locally or update CI

Pattern 2: Linter Version Drift

Symptoms:

  • "Works locally but CI fails on linting"
  • New rules in CI not enforced locally
  • Formatting differences

Fix:

# Sync pre-commit hooks to latest
pre-commit autoupdate

# Or pin specific version
pip install ruff==<ci-version>

Pattern 3: Missing Dependencies

Symptoms:

  • ModuleNotFoundError in CI
  • Optional dependencies not installed

Fix:

# Install all optional dependencies
pip install -e ".[dev]"

# Ensure requirements.txt is up to date
pip freeze > requirements.txt

Output Format

## Dependency Resolver Report

### Environment Comparison

| Component | Local   | CI      | Status   |
| --------- | ------- | ------- | -------- |
| Python    | 3.12.10 | 3.11    | MISMATCH |
| ruff      | 0.12.7  | 0.13.0  | MISMATCH |
| pyright   | 1.1.350 | 1.1.350 | OK       |

### Mismatches Found: 2

### Recommendations

1. **Python Version** (CRITICAL)
   - Local: 3.12.10, CI: 3.11
   - Action: Consider using pyenv to test with CI version before push
   - Risk: Type syntax differences may cause failures

2. **ruff Version** (WARNING)
   - Local: 0.12.7, CI: 0.13.0
   - Action: Run `pip install ruff==0.13.0` or `pre-commit autoupdate`
   - Risk: New rules may flag previously passing code

### Quick Fix Commands

Sync ruff version

pip install ruff==0.13.0

Update all pre-commit hooks

pre-commit autoupdate

Re-run pre-commit to validate

pre-commit run --all-files


### Status: ACTION REQUIRED

Push may fail due to environment mismatches.
Run recommended fixes before pushing.

When to Use This Skill

Trigger Signs:

  • "CI is failing but it works locally"
  • "Linting passes here but not in CI"
  • Before pushing after long development session
  • After updating local Python or tools
  • When onboarding to new project

Not Needed When:

  • CI already passing consistently
  • Environment just synced
  • Only editing documentation

Related Resources

  • DISCOVERIES.md: CI Failure Resolution Process Analysis (lines 836-914)
  • fix-agent.md: Templates for import/config/CI fixes
  • ci-diagnostic-workflow.md: Post-push CI failure resolution
  • pre-commit-diagnostic.md: Pre-commit hook failures
  • .github/workflows/ci.yml: CI configuration source of truth

Philosophy Alignment

Ruthless Simplicity

  • Procedural approach: Five clear steps, no unnecessary abstraction
  • Direct shell commands: Users can copy-paste recommendations
  • Focused scope: Only detects environment mismatches, delegates fixes to existing agents

Zero-BS Implementation

  • Actionable output: Every recommendation includes exact commands
  • No theoretical advice: Specific version numbers and file paths
  • Pre-push prevention: Catches issues before wasted CI cycles

Modular Design

  • Clean hand-offs: Integrates with fix-agent, pre-commit-diagnostic, ci-diagnostic-workflow
  • Single responsibility: Detection and comparison only; fixes delegated to specialized agents
  • Regeneratable: Can be rebuilt from this specification

平台分布

Claude Code

25.21%
按下载量换算214

OpenCode

22.06%
按下载量换算187

Antigravity

17.88%
按下载量换算151

Gemini CLI

11.4%
按下载量换算97

windsurf

8.15%
按下载量换算69

Cursor

3.78%
按下载量换算32

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/rysweet/amplihack --skill dependency-resolver;npx skills add rysweet/amplihack --skill "dependency-resolver" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

继续浏览同类 Skills