Six skills I built for Claude Code - repo coherence, air-gapped debugging, and sorting my shopping list into aisle order
▲ 4 r/BuildWithClaude+1 crossposts

Six skills I built for Claude Code - repo coherence, air-gapped debugging, and sorting my shopping list into aisle order

I've been building skills to fix things that kept biting me. Six of them, all MIT and free to try, no paid tier and nothing to sign up for.

**dovetail** \- checks whether a repo still agrees with itself. Dead links, dangling anchors, orphaned files, docs that drifted from the code, conventions the repo states but doesn't follow. The deterministic half is plain Python with no network and no model, so it runs fast enough to gate a build.

**heliograph** \- debug a machine you can't log into, through an operator who can't debug it. A git repo is the transport in both directions. For air-gapped and change-controlled estates.

**verve** \- strips AI tells from prose, British English. Explicitly not a detector-evasion tool, and it says so if you ask it to be one.

**legwork** \- research where every claim states how well it's supported, and says when the evidence can't settle the question.

**outlook-graph** \- Microsoft 365 mail and calendar via Graph, plus PST archives into searchable markdown.

**trello** \- boards, lists and cards, plus board digests and a due-date radar. The pack also has the one I use most and expected least: it reorders a shopping list into the aisle order of an actual supermarket, prefixing a food-type emoji to every card, so you walk the shop once instead of doubling back. Store layout comes from a preset - Tesco by default, any shop if you write one.

**How Claude helped:** all six were written with Claude Code, and the interesting part was that the skills started changing how the next one got built. Dovetail found stale docs in its own siblings. Verve got used on their READMEs. The format itself imposed discipline too, because a skill is loaded on its description alone - if you can't say what it does in two lines, it's badly scoped and you find that out immediately.

[https://github.com/dbhq-uk\](https://github.com/dbhq-uk)

u/grinidx — 2 days ago
▲ 2 r/dotnet

Vela v1.0.0 - compiler-exact .NET code search from a SCIP index, Razor and Blazor included

Grep can't tell you a property is used from a Razor view. That gap has cost me more time than anything else on legacy ASP.NET work - you rename something, the build is green, and a .cshtml three folders away breaks at runtime.

Vela builds a SCIP index of a solution with Roslyn, then answers "find references", "who calls this" and "what would a change break" from that database. It covers C#, VB, Razor Pages, MVC views and Blazor components, so the Razor side is indexed rather than skipped.

Two consequences of the SCIP approach that I didn't expect going in:

The index is worth paying for once. A def lands in about 0.55s, a refs returning 3,156 results in about 1.3s, on a 0.09s process floor. Loading the same solution into a live Roslyn workspace costs 9.3s plus 23.8s to compile the web project - and it costs that on every invocation, because nothing stays resident.

SCIP is an interchange format. A scip-typescript index imports beside the C# one and both answer from the same database, so a polyglot repo gets one query surface. Languages it can't index itself are declared in a vela.json and it refuses to pretend they're covered - missing language, banner on every answer, non-zero exit.

Honest gap: it won't answer "what implements this interface" yet. That's a SCIP relationship and it doesn't emit those.

It's a skill for Claude Code and Codex rather than an IDE extension, so the agent gets the compiler's answer instead of guessing from a text search. 426 hermetic tests. Deterministic - same solution at the same commit, same answer, no model calls and no network. Read-only; it never writes to the repo it indexes.

MIT, v1.0.0: https://github.com/dbhq-uk/vela-skill

reddit.com
u/grinidx — 3 days ago