scip-core

Encode code indexing data in a protobuf-based SCIP Index schema.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/hafley66/claude-research --skill scip-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scip-core
Source: https://github.com/hafley66/claude-research/tree/main/skills/scip/scip-core
Command: npx skills add https://github.com/hafley66/claude-research --skill scip-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SCIP core defines a standard protobuf-based encoding for code indexing, enabling language-agnostic navigation such as go to definitions, references, and implementations across projects.

Core Features & Use Cases

  • Protobuf-based Index schema with Metadata, Document, and SymbolInformation for defining and linking code symbols.
  • Document representation with occurrences and ranges enabling precise symbol locations and navigation.
  • Cross-repo symbol information through external_symbols to support hover docs and relationships.

Quick Start

Run an SCIP indexer against your repository to generate an index.scip file.

Frequently Asked Questions about scip-core

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is SCIP code indexing and how does it work?

SCIP code indexing encodes code symbols and their relationships in a protobuf-based Index format. It enables language-agnostic navigation like go-to-definition, references, and hover documentation across complex codebases and project boundaries.

How do I generate a SCIP index for cross-repo symbol navigation?

To generate a SCIP index, run a SCIP indexer against your repository to produce an index.scip file. This file encodes Metadata, Documents, and external_symbols according to the SCIP protobuf schema for symbol lookup.

Does SCIP indexing work across multiple programming languages and repositories?

Yes, SCIP indexing applies across languages and project boundaries. It uses external_symbols to support cross-repo symbol lookup, hover documentation, and relationship navigation for complex codebases.

What is the best way to standardize code navigation data for go-to-definition and hover docs?

Defining a standard protobuf-based encoding for code indexing is the best way to standardize navigation data. SCIP core provides an Index schema with Metadata, Document, and SymbolInformation to link code symbols and enable precise symbol locations.

Do I need a specific indexer to create a SCIP index file?

Yes, you need an SCIP indexer to emit an Index containing Metadata, Documents, and external_symbols. The indexer processes your repository to generate an index.scip file conforming to the SCIP protobuf schema.

How are symbol locations and occurrences represented in a SCIP index?

Symbol locations and occurrences are represented through Document structures containing occurrences and ranges. This precise representation in the SCIP protobuf schema enables accurate go-to-definition and symbol navigation.