RepoPilot

albert-weasker / niubigeo

Search albert-weasker/niubigeo

GitHub

Code

Understand albert-weasker/niubigeo's source layout and find a starting point for your task using the saved repository evidence.

A
Architecture grade
score 99/100
0
Import cycles
lower is better
235
Modules parsed
35 edges
97%
Layeredness
clean-layer ratio

Measured from the parsed import graph. Coupling, not a reading order.

Module map

Shade by
Entry points and orchestratorsShared coreFoundationStandalonesrc184 files · 19 commitsexamples9 files · 2 commitsscripts26 files · 6 commitsplaywright.config1 file · 1 commitplaywright.custom-models.config1 file · 1 commitplaywright.keyword-monitor.config1 file · 1 commitplaywright.localization.config1 file · 2 commitsplaywright.phase2.config1 file · 1 commitplaywright.phase3.config1 file · 1 commitplaywright.phase4.config1 file · 1 commitplaywright.phase5.config1 file · 1 commitplaywright.real-provider-10.config1 file · 1 committest0 files · 15 commits

13 modules, 4 links. A link means one module imports another; thicker lines mean more imports. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.

src1842019Foundation
examples9212Shared core
scripts26026Entry or leaf
playwright.config1001Standalone
playwright.custom-models.config1001Standalone
playwright.keyword-monitor.config1001Standalone
playwright.localization.config1002Standalone
playwright.phase2.config1001Standalone
playwright.phase3.config1001Standalone
playwright.phase4.config1001Standalone
playwright.phase5.config1001Standalone
playwright.real-provider-10.config1001Standalone
test00115Entry or leaf

Where to start reading

  1. Repository root
  2. Repository root
  3. Runtime candidatename match
  4. Runtime candidatename match
  5. Suggested starting pointAI
  6. Suggested starting pointAI
  7. Suggested starting pointAI
  8. Suggested starting pointAI

Find files for a task

AI

Add a new LLM provider

  • Register provider in model catalog with capability mappings (supported models, token limits)
  • Add provider case to routing logic in prompt execution to select provider for analysis tasks
  • Update environment configuration schema to include new provider credentials

Add a new analysis metric

  • Define metric schema and type in core domain model
  • Create analyzer module (src/analyzer/yourmetric.ts or src/metrics/yourmetric.ts) implementing metric extraction logic
  • Integrate analyzer into audit runner observation processing pipeline
  • Add metric to report builder output sections and dashboard model

Add a new monitoring task type

  • Define task schema with recurrence rules and target parameters
  • Implement task handler logic in monitoring service dispatch
  • Create event builder for task result recording
  • Update schedule worker to recognize and execute new task type

Trace runtime behavior

Add or update tests

Change build or automation

File paths come from a snapshot of up to 500 captured paths; an omitted file may still exist.

  • Public and runtime candidates are based on file names; their exports and execution paths still need checking in source.

Code quality and hotspots

Largest source files

  • Branch points195 per file on average
  • Code issues0 errors, 375 warnings
  • Largest file2,577 lines
  • Hotspot load0 high-risk files

Static checks on the 15 largest source files.

Tests, CI and tooling

  • CIGitHub Actions4 workflows
  • Tests62 test filesJest/Vitest · Playwright · 0.27 test files per source file (file count, not coverage)
  • Dependency updatesNo config detected
  • CI pass rate28%last 50 runs
  • First reply to issues10 hoursmedian of 15 recent issues

Test folders: test · e2e · test/fixtures

Hotspots

Files that change often and branch heavily, highest first. Complexity is 0–100 from branch and nesting counts.