gitnexus-plus: A DSH plugin that reveals GitNexus index blind spots for DeepSeek Harness

What Does It Do?

GitNexus Plus is a DSH plugin for DeepSeek Harness that makes a GitNexus index's blind spots visible, starting with the one thing GitNexus cannot tell you: what the index left out. gitnexus analyze silently drops large files and mentions it only in a single stderr line that is never returned, persisted, or queryable. This plugin turns that line into structured data, a tool, and a view, so you can see skipped files, index freshness, and the gap between git activity and the graph.

Core Features

• Skipped-file inventory: lists ignored large files with path, size, and share of their language, and explains why each is not source using two independent signals, a single-line minification heuristic and a build-output path heuristic; binary assets are detected separately and never labeled minified.
• Index freshness: compares the indexed commit against HEAD, classifying it as current, behind, diverged, or unknown, and reports the count of uncommitted changes.
• Graph composition and query surfaces: reads nodes, edges, communities, processes, embeddings, and edges-per-node from the manifest, and states which of graph, keyword, and semantic search are actually available, with the reason when one is not.
• Three-way git verdicts: crosses recent commits, authors (bots marked), branches, most-changed and most-recent files with the index, labeling each file indexed, excluded by design, or missing from the index; only the last raises a warning.
• Language bytes and resolver confidence: splits languages by bytes into parseable, merely recognized, and everything else, and reports untyped receiver sites that make impact and context a lower bound rather than an exact answer.

How to Use This Plugin?

After enabling it in DSH, run the coverage report to get a full health check of an index, optionally pointing it at a specific repository directory. The plugin is strictly read-only: it never triggers analyze, writes to .gitnexus/, or takes the index lock, so checking status can never start a 30-second rebuild. To answer which files were skipped it reuses GitNexus's own ignore filter and language detection instead of approximating them; if upstream reshapes those modules it degrades to a documented fallback scan rather than reporting a wrong number. For legacy indexes without coverage metadata, the size cap is reported as unknown with a note instead of being defaulted to today's value.

How to Troubleshoot This Plugin?

If the report shows the scan running in fallback mode, upstream GitNexus module structure has changed and the plugin can no longer reuse its native scan logic; the numbers remain usable but should be read per the documented fallback behavior. If an older index carries no coverage information, the size cap appears as unknown, which is expected rather than an error and should not be read as evidence that files were skipped.