arib-graph

Generate a JSON import graph of monorepo file dependencies using ripgrep.

2|Updated Apr 19, 2026

Search Tags:#refactoring #navigation #monorepo #ripgrep #dependency-mapping #code-graph

Ready to run

npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-graph

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: arib-graph
Source: https://github.com/AribSudia/claude-code-methodology/tree/main/.claude/skills/arib-graph
Command: npx skills add https://github.com/AribSudia/claude-code-methodology --skill arib-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ripgrep, jq, and includes scripts (resource) components.

What problem does it solve?

This Skill solves the difficulty of navigating large monorepos by providing a structural map of file imports, preventing the need for repetitive, expensive full-tree grepping during every session.

Core Features & Use Cases

Structural Mapping: Generates a git-diffable JSON graph of file-to-file import relationships.
On-Demand Querying: Allows users to identify which files import a specific entity or what a specific file imports without keeping the graph in the active token context.
Use Case: When refactoring a core service, use this to instantly identify all dependent files that might be impacted by a change, ensuring safer and faster architectural updates.

Quick Start

Use the arib-graph skill to build the initial import graph for the current repository.

Frequently Asked Questions about arib-graph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I map import dependencies in a monorepo for refactoring?▼

To map import dependencies in a monorepo for refactoring, generate a structural JSON graph of file-to-file relationships. This identifies all dependent files impacted by changes, preventing repetitive full-tree grepping and ensuring safer architectural updates.

What is the best way to navigate code imports without semantic overhead?▼

The best way to navigate code imports without semantic overhead is using a lightweight structural code-graph. This maps file dependencies using ripgrep, allowing on-demand querying of import relationships without keeping the graph in the active token context.

Do I need ripgrep and jq installed to generate a code-graph manifest?▼

Yes, you need ripgrep and jq installed in your shell environment to generate a code-graph manifest. These dependencies process file imports and query the resulting JSON graph manifest for efficient code navigation and impact analysis.

Can I identify which files import a specific entity in a large repository?▼

Yes, you can identify which files import a specific entity in a large repository using on-demand querying. The generated structural import graph allows you to instantly find dependent files without expensive full-tree grepping during every session.

How does a git-diffable JSON graph help with monorepo impact analysis?▼

A git-diffable JSON graph helps with monorepo impact analysis by storing structural file-to-file import relationships. This allows you to track architectural changes over time and instantly identify all dependent files affected by refactoring a core service.