Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Feature Request: Support Codebase Semantic Indexing for Neovim

オープン
  • 何か問題がありますか？
#306 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
neovim
領域
developer-experience, tooling

調査の方向性

Start by reading the existing copilot.vim LSP infrastructure and checking whether the underlying Copilot service supports repository indexing. Define how a repository index would be built, updated, queried, and supplied to requests, then verify the proposed command and cross-file retrieval against a large repository.

索引モデルが issue の本文から書いたものです。

説明

Feature Request: Support Codebase Semantic Indexing for Neovim

GitHub Copilot in VS Code provides Codebase Semantic Indexing, including the Chat: Build Codebase semantic index command. This is very useful when working with large repositories because Copilot can identify and retrieve relevant files and code across the codebase.

It would be very valuable to have similar functionality available in Neovim through copilot.vim.

Motivation

For a small/local coding task, the current Copilot experience works well. However, for a large codebase, repository-level context becomes increasingly important.

Without semantic codebase indexing, Neovim users may need to manually navigate to relevant files and provide context through multiple interactions. This can make large-codebase tasks less efficient and potentially result in significantly more context/tokens being used.

For example, for a request such as:

"Add a new workflow similar to the existing payment workflow."

Copilot should ideally be able to discover the relevant controllers, services, interfaces, implementations, configuration, and tests across the repository rather than relying primarily on the currently open files.

Proposed feature

Provide a way to build and maintain a semantic index of the current repository, similar to VS Code's:

Chat: Build Codebase semantic index

For example:

:Copilot build-codebase-index

The implementation could ideally reuse existing Copilot/LSP infrastructure if the underlying Copilot service already supports repository indexing.

Useful capabilities would include:

  • Build an index for the current repository
  • Incrementally update the index as files change
  • Search/retrieve relevant code and symbols for Copilot requests
  • Support repository-level and cross-file questions
  • Use retrieved context when generating or modifying code
  • Avoid sending unnecessary repository content to the model
Expected benefit

This would make Copilot in Neovim much more effective for large repositories, especially for:

  • Multi-file feature implementation
  • Refactoring
  • Cross-file code understanding
  • Large-scale code generation
  • Finding relevant implementations and call paths
  • Reducing unnecessary context/token usage

VS Code already provides this capability, so bringing equivalent repository-level semantic indexing to Neovim would significantly improve the large-codebase experience.

Thank you!

主要言語
Vim Script
スター
11.7k
フォーク
821
30日以内にマージされた PR はありません

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/copilot.vim のほかの issue

github/copilot.vim の issue をすべて見る

似ている issue

DevTools の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。