integrations-and-extensions
Handle code-review-graph custom languages, embeddings, wiki, registry, daemon, GitHub Action, and eval workflows.
- License 许可
- MIT
- 最近更新
- 2026-10-08
- Stars
- ★ 11
- Forks
- 3
01 前言 Front Matter
- name
- integrations-and-extensions
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Handle code-review-graph custom languages, embeddings, wiki, registry, daemon, GitHub Action, and eval workflows.
- disable-model-invocation
- true
02 资源文件 6
- 参考文档references/custom-languages.md1.9 KB
- 参考文档references/embeddings.md2.0 KB
- 参考文档references/eval.md1.1 KB
- 参考文档references/github-action.md1.5 KB
- 参考文档references/registry-and-daemon.md1.7 KB
- 参考文档references/troubleshooting.md3.3 KB
03 SKILL.md 正文
Integrations and Extensions
Use this sub-skill for advanced or optional workflows: custom parser languages, semantic embeddings, wiki generation, multi-repo registry and daemon support, GitHub Action integration, and evaluation/benchmark guidance.
Start here
- Confirm the requested feature is truly optional or integration-focused.
- Read the narrow reference for the exact surface.
- Install only the extra needed for that surface, not
allby default.
Read references/custom-languages.md for .code-review-graph/languages.toml workflows. Read references/embeddings.md for semantic-search and provider behavior. Read references/registry-and-daemon.md for multi-repo registry, watch daemon, and repo listing. Read references/github-action.md for PR review automation. Read references/eval.md for benchmark/reproduction guidance. Read references/troubleshooting.md when an optional dependency, provider, grammar, daemon state, or eval run fails.
Route by task
| User task | Do this |
|---|---|
| "Add a custom language" | Edit .code-review-graph/languages.toml and rebuild the graph. |
| "Enable semantic search" | Install the embeddings extra, then run the embedding workflow. |
| "Generate wiki pages" | Use the wiki generation workflow after communities exist. |
| "Register multiple repos" | Use the registry/daemon commands. |
| "Run a PR review in CI" | Use the GitHub Action pattern and the bundled PR renderer. |
| "Reproduce benchmarks" | Follow the eval reference and be prepared for expensive, repo-clone-heavy work. |
Optional dependency policy
Only install an optional extra when the task requires it:
code-review-graph[embeddings]for local sentence-transformers embeddings.code-review-graph[google-embeddings]for Google Gemini embeddings.code-review-graph[communities]for igraph-based community detection.code-review-graph[wiki]for Ollama-backed wiki summaries.code-review-graph[eval]for benchmark and report helpers.code-review-graph[enrichment]for deeper Python call-resolution enrichment.
Do not install all unless the user explicitly wants every optional feature in one environment.
Safe starting points
- Custom language users should start with a small
.code-review-graph/languages.tomland a rebuild. - Embedding users should confirm provider/environment variables before enabling cloud providers.
- Registry/daemon users should ensure each registered repository has a valid graph or watchable checkout.
- GitHub Action users should prefer the split analysis/comment workflow for fork safety.
Boundaries
- For installation and server setup, use
install-and-setup. - For diff review and PR comments, use
review-changes. - For structural exploration, search, and refactor previews, use
graph-exploration.
Verification anchors
Native tests that ground this route include custom-language tests, embeddings tests, registry and daemon tests, wiki tests, eval tests, and PR workflow security tests. Some of these are optional or service-backed; record unverified optional capabilities explicitly instead of implying full support.
04 同仓库更多 Skills
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
obsidian-clipper-template-creator
Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.
python-api
Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP/mAP semantics, and source-style import diagnostics.
file-evaluation
Folder-based PASCAL VOC AP/mAP evaluation from ground-truth and detection text files.
object-detection-metrics
Guides legacy Object-Detection-Metrics PASCAL VOC AP/mAP evaluation from detection text folders and direct Python API classes.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.