Code
How graphify-labs/graphify is laid out, and where to start for common changes.
There is no import map for this report yet.
Where to start reading
- Repository root
- Repository root
- Likely public API
- Likely public API
- Likely start-up file
- Likely start-up file
- Suggested starting pointAI
- Suggested starting pointAI
Find files for a task
AIAdd support for a new programming language
- Create a new language extractor by subclassing from `graphify/extractors/base.py`
- Implement required methods: `extract()`, `parse_import()`, and language-specific AST traversal
- Register the new extractor in the dispatcher within `graphify/extractors/engine.py`
- Update language detection logic in `graphify/detect.py` to recognize source files
Add a new export format
- Create a new exporter by subclassing from `graphify/exporters/base.py`
- Implement `export()` and `export_relations()` methods to serialize graph nodes and edges
- Wire the exporter into the CLI command selection in `graphify/cli.py`
Extend graph analysis with custom metrics
- Add analysis logic to `graphify/analyze.py` to compute new graph properties
- Update `graphify/global_graph.py` to store and propagate new metric types
- Expose metrics in exporter implementations (e.g., `graphify/exporters/html.py`)
Add a new AI assistant skill integration
- Document query patterns, exports, and hooks in `references/` markdown files
- Configure assistant-specific integration in `graphify/always_on/` or skill entry point
Change the public API
Trace runtime behavior
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.