abhigyanpatwari / gitnexus

GitHub

Code

How abhigyanpatwari/gitnexus is laid out, and where to start for common changes.

Architecture grade

score 100/100

Import cycles

lower is better

329

Files mapped

10 imports between them

100%

Layering

of imports point one way

From the map of which files import which, built when the code was last read in full. It shows what depends on what, not a reading order.

Module map

Shade by

Fade vendored code

5 modules, 1 links. A link means one module imports another; thicker lines mean more imports. Links come from 329 of 1,462 source files, so the real counts are higher. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.

Where to start reading

Repository root
Repository root
Likely public API
Likely public API
Suggested starting pointAI
Suggested starting pointAI
Suggested starting pointAI
Suggested starting pointAI

Find files for a task

Add a new CLI command

Implement command handler exporting a named function matching the pattern used in analyze.ts.
Register command in CLI dispatcher by updating the command router in the main entry point.

Add a new AI skill for Claude

Create skill documentation directory under gitnexus/skills/ (e.g., gitnexus/skills/gitnexus-my-skill/).
Reference skill in Claude hook configuration gitnexus/hooks/claude/gitnexus-hook.cjs for discovery and activation.

Add support for a new programming language

Extend language detection in gitnexus/src/cli/analyze.ts to trigger new parser for target file extensions.

Change the public API

Add or update tests

Change build or automation

RepoPilot lists up to 500 files, so a file missing here may still exist.

Files marked “likely” are guessed from their names.

Code quality and hotspots

Largest source files

Branch points230 per file on average
Code issues1 error, 82 warnings
Largest file2,893 lines
Hotspot load10 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

CIGitHub Actions32 workflows
Tests5,336 test filesJest/Vitest · Pytest · 3.6 test files per source file (file count, not coverage)
Dependency updatesCodeQL · Trivy

Test folders: eval/tests · .devcontainer · .github/scripts/triage

Hotspots

gitnexus/src/cli/analyze.ts65 commits in 180 days · 342 branch points
gitnexus/src/cli/setup.ts22 commits in 180 days · 203 branch points
gitnexus/src/core/group/extractors/http-patterns/java.ts19 commits in 180 days · 214 branch points
gitnexus/src/core/group/extractors/http-route-extractor.ts19 commits in 180 days · 179 branch points
gitnexus/src/core/embeddings/embedding-pipeline.ts18 commits in 180 days · 157 branch points
gitnexus/src/core/group/bridge-db.ts15 commits in 180 days · 108 branch points
gitnexus/src/core/group/sync.ts15 commits in 180 days · 94 branch points
gitnexus/src/core/group/extractors/http-patterns/python.ts14 commits in 180 days · 262 branch points

Files that change often and branch heavily, highest first. Branch points count if, loop, case, catch, ternary, && and || in the file.