configflux

Weld

Name: Weld
Author: configflux

Development community

SOURCE https://github.com/configflux/weld

Description

Weld connected structure toolkit for agent-first repository discovery

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Weld

[![CI](https://github.com/configflux/weld/actions/workflows/ci.yml/badge.svg)](https://github.com/configflux/weld/actions/workflows/ci.yml) [![PyPI](https://img.shields.io/pypi/v/configflux-weld.svg)](https://pypi.org/project/configflux-weld/) [![Python versions](https://img.shields.io/pypi/pyversions/configflux-weld.svg)](https://pypi.org/project/configflux-weld/) [![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)

A local codebase graph for AI coding agents. Weld scans code, docs, CI, build files, runtime configs, and repo boundaries into a deterministic graph. Agents can query this graph through CLI or MCP instead of rediscovering the repository from scratch every session.

The graph lives on disk (`.weld/graph.json`), stays under your control, and answers the questions agents and humans repeatedly ask about a codebase: where a capability lives, which docs are authoritative, what build and test surfaces a change touches, and what boundaries constrain the implementation.

**Evaluators: start with v0.23.1.** v0.23.1 is the current recommended starting point. Headline features added since v0.14.0: a 14-tool MCP server for graph-backed agent context (`weld_query`, `weld_find`, `weld_context`, `weld_path`, `weld_brief`, `weld_stale`, `weld_callers`, `weld_references`, `weld_export`, `weld_trace`, `weld_impact`, `weld_enrich`, `weld_diff`, `weld_review`); `wd impact` blast-radius queries driven by node, file list, working tree, or git diff range, with a stale-graph gate; `wd review` JSON-first triage for speculative edges; an end-to-end C# strategy stack (solution/project parsing, MSBuild targets, test-framework detection, ASP.NET routes, EF Core, inheritance edges, per-method call graphs) that auto-wires on `wd init` when matching artifacts are present; `wd init` auto-wiring of the interface strategies (gRPC `.proto`