splice

Version: 2.8.0

Span-safe refactoring kernel for 7 languages. Byte-accurate code editing with graph algorithm analysis.

Positioning: Precision editing tool for codebases indexed by Magellan. Use for cross-file rename, impact analysis, and verified refactoring.

Purpose

splice edits code with graph-aware safety. Built for:

• Developers — Cross-file rename, safe refactoring with rollback
• Grounded Assistants — Byte-accurate edits with proof-based verification
• Tooling — Scriptable transformations with AST validation

Features

• Span-safe editing — Byte-accurate replacements with tree-sitter validation
• Cross-file rename — Symbol rename across entire codebase
• Graph algorithms — Reachability, dead-code, cycles, condense, slice
• Impact analysis — Blast zone detection before editing
• Proof-based refactoring — Machine-checkable behavioral equivalence
• Code completion — Grounded, import-aware suggestions using Magellan database
  • Cross-file symbol resolution via import tracking
  • Distinguishes local vs imported symbols with source tracking
  • Token filtering and enhanced ranking for imported symbols
  • Performance: low-millisecond internal query time on indexed project databases
• 7 languages — Rust, Python, C, C++, Java, JavaScript, TypeScript
• Library API — Use as a Rust crate for programmatic refactoring (forge, agents)

Quick Start

# Install
cargo install splice

# Requires Magellan database (create first)
magellan watch --root ./src --db .magellan/splice.db

# Check status
splice status --db .magellan/splice.db

# Find reachable code from main
splice reachable --symbol main --path src/main.rs --db .magellan/splice.db

# Cross-file rename
splice rename --symbol old_name --to new_name --path src/lib.rs --db .magellan/splice.db

# Code completion (import-aware)
splice complete --file src/lib.rs --line 27 --column 8 --db .magellan/splice.db --max-results 10

Library Usage

Splice exposes a library API for programmatic use. Add to Cargo.toml:

[dependencies]
splice = { version = "2.8", default-features = false, features = ["sqlite"] }

High-Level API (forge integration)

use splice::forge;

// Patch a symbol with new content (resolves via SymbolNavigator)
let result = forge::patch_symbol_in_file(
    Path::new("src/lib.rs"),
    "my_function",
    "pub fn my_function() -> i32 { 42 }",
    Path::new(".magellan/myproject.db"),
)?;

// Rename across all files
let result = forge::rename_symbol_across_files("old_name", "new_name", db_path)?;

// Preview without writing
let preview = forge::preview_patch_symbol(file, symbol, content, db)?;

// Resolve symbol to byte span
let span = forge::resolve_symbol_span(file, symbol, db)?;

Low-Level API

use splice::patch::{replace_span, apply_patch_with_validation, SpanReplacement};
use splice::graph::rename::{apply_replacements_in_file, group_references_by_file};
use splice::workspace::{find_workspace_root, detect_project_language};
use splice::verify::{pre_verify_patch, post_verify_patch};

Installation

cargo install splice

Backends

Requirements

• Magellan 4.2+ — Required for code graph
• sqlitegraph 3.0.3+ — Included automatically

Documentation

• MANUAL.md — Complete command reference and examples
• CHANGELOG.md — Version history
• docs/API.md — Library API reference
• docs/completion.md — Code completion feature documentation

What splice Does NOT Do

• Index code (use Magellan)
• Search code (use llmgrep)
• CFG analysis (use Mirage)
• Type checking (use Compiler/LSP)

License

GPL-3.0. See LICENSE.