菜单
GitNexus code intelligence skill for analyzing repos. Run gitnexus analyze, query, cypher, context, and impact commands against indexed repositories. Auto-detects and installs gitnexus@1.6.3 if missing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate and critically evaluate grounded improvement ideas for the current project. Use when asking what to improve, requesting idea generation, exploring surprising improvements, or wanting the AI to proactively suggest strong project directions before brainstorming one in depth. Triggers on phrases like 'what should I improve', 'give me ideas', 'ideate on this project', 'surprise me with improvements', 'what would you change', or any request for AI-generated project improvement suggestions rather than refining the user's own idea.
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a tech plan', 'plan the implementation', 'how should we build', 'what's the approach for', 'break this down', 'plan a trip', 'create a study plan', or when a brainstorm/requirements document is ready for planning. Use for plan deepening when the user says 'deepen the plan', 'deepen my plan', 'deepening pass', or uses 'deepen' in reference to a plan.
[BETA] Execute work with external delegate support. Same as gh:work but includes experimental Codex delegation mode for token-conserving code implementation.
Execute work efficiently while maintaining quality and finishing features
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/ for accuracy, when a recently solved problem contradicts an existing learning, when pattern docs no longer reflect current code, or when multiple docs seem to cover the same topic and might benefit from consolidation.
Document a recently solved problem to compound your team's knowledge or update CONCEPTS.md, the project's shared domain vocabulary.
| name | gh:nexus |
| description | GitNexus code intelligence skill for analyzing repos. Run gitnexus analyze, query, cypher, context, and impact commands against indexed repositories. Auto-detects and installs gitnexus@1.6.3 if missing. |
| argument-hint | [analyze <repo-path> | status | query <query> | cypher <cypher> | context <symbol> | impact <symbol>] |
Analyze repositories with GitNexus to extract code intelligence — symbols, dependencies, call graphs, and impact analysis.
License Caution: GitNexus is distributed under the PolyForm-Noncommercial-1.0.0 license. Use in commercial contexts requires a separate license. This skill is a convenience wrapper; license compliance is your responsibility.
Boundary Notes: GitNexus integration is optional and non-blocking. If gitnexus is unavailable and cannot be installed, the skill reports the limitation and stops gracefully rather than failing the session.
| Command | Description |
|---|---|
gh-nexus analyze <repo-path> | Run gitnexus analyze on the target repository to index it for queries |
gh-nexus status | Check local GitNexus registry status (indexed repos, db health) |
gh-nexus query <query> | Best-effort natural language query against indexed repos (experimental) |
gh-nexus cypher <cypher> | Run a Cypher query against the indexed repo graph database |
gh-nexus context <symbol> | Get full context for a symbol (definition, references, call chain) |
gh-nexus impact <symbol> | Get impact analysis for a symbol (who calls it, what breaks if changed) |
Before running any command, detect whether gitnexus is available:
command -v gitnexus >/dev/null 2>&1
If missing, attempt installation in this order:
Global npm install (preferred for repeated use):
npm install -g gitnexus@1.6.3
npx fallback (no global install needed):
npx --yes gitnexus@1.6.3 <command>
After install, verify:
gitnexus --version
If both methods fail, report:
"GitNexus is not available and could not be installed. Please install manually:
npm install -g gitnexus@1.6.3"
Then stop gracefully — do not block the caller's workflow.
command -v gitnexus (or shutil.which("gitnexus") in Python)| Subcommand | gitnexus equivalent | Notes |
|---|---|---|
analyze <repo-path> | gitnexus analyze <repo-path> | Indexes the repo; may take time for large codebases |
status | gitnexus status | Shows registry state, indexed repos, db size |
query <query> | gitnexus query "<query>" | Best-effort NL query; experimental quality |
cypher <cypher> | gitnexus cypher "<cypher>" | Direct Cypher against the graph; requires indexed repo |
context <symbol> | gitnexus context <symbol> | Symbol resolution (function, class, variable) |
impact <symbol> | gitnexus impact <symbol> | Change-impact analysis for the symbol |
For npx fallback usage, prefix commands with npx --yes gitnexus@1.6.3 instead of gitnexus.
analyze, note that indexing is async/background and may need a moment before queries workquery, flag that results are experimental and should be verified| Scenario | Response |
|---|---|
| gitnexus not found, install fails | Graceful stop with manual install instructions |
| Repo not indexed | Suggest running gh-nexus analyze <repo-path> first |
| Cypher syntax error | Pass through gitnexus error; suggest checking Cypher syntax |
| Symbol not found | Report "Symbol not found in indexed repo" |
| Query returns empty | Report "No results — try rephrasing or check if repo is indexed" |