Stay updated — Join the build list for tutorials and AI insights. No spam.

Workflows

Daily development workflows using Graphify for architecture questions, dependency tracing, and impact analysis.

Workflows

Common Graphify workflows for daily development — from architecture questions to impact analysis.

📖 Documentation in This Section

🎯 Quick Reference

Most Common Commands

 1# Always signal activity first!
 2mkdir -p graphify-out && touch graphify-out/.graphify-activity
 3
 4# Architecture overview
 5graphify query "project overview"
 6
 7# How a system works
 8graphify query "how does the X pipeline work?"
 9
10# What depends on a file
11graphify query "what depends on path/to/file.py?"
12
13# Trace relationship
14graphify path A B
15
16# Deep-dive on component
17graphify explain path/to/file.py

When to Rebuild

1# Signal activity
2mkdir -p graphify-out && touch graphify-out/.graphify-activity
3
4# Rebuild after significant changes
5graphify update . --code-only   # code only
6graphify update .               # full (needs API key)

Rebuild triggers: 5+ files changed, branch merged, graph >4 hours old, references deleted files.


For Different Scenarios

🔍 Exploring a New Codebase

1# 1. Get the big picture
2graphify query "project overview"
3
4# 2. Understand main systems
5graphify query "what are the main subsystems?"
6
7# 3. Drill into interesting areas
8graphify query "how does the authentication system work?"
9graphify explain path/to/auth/module.py

🐛 Debugging / Understanding Bugs

1# 1. Find related code
2graphify query "where is user authentication handled?"
3
4# 2. Trace the flow
5graphify path path/to/login.py path/to/session.py
6
7# 3. Check dependencies
8graphify query "what depends on the session module?"

🔧 Refactoring / Impact Analysis

1# 1. Before changing a file, check what depends on it
2graphify query "what depends on path/to/shared/utility.py?"
3
4# 2. Trace call chains
5graphify path path/to/utility.py path/to/consumer.py
6
7# 3. After refactor, rebuild
8graphify update . --code-only

📝 Writing Documentation

1# 1. Get accurate architecture description
2graphify query "describe the data flow from YouTube URL to Hugo page"
3
4# 2. Find all related files
5graphify query "list all files in the vocabulary extraction pipeline"
6
7# 3. Verify relationships
8graphify path scripts/dictionary/extract_vocab.py data/dictionary/output.yaml

Next Steps

In this section

  • Daily Usage
    Most common Graphify query patterns for daily development work.
  • Architecture Queries
    Advanced architecture questions for system understanding, design reviews, and onboarding.
  • Dependency Tracing
    Trace relationships between components, find call chains, and understand data flow using graphify path.
  • Impact Analysis
    Assess the impact of changes before refactoring — find dependents, trace ripple effects, and plan safe modifications.