Find your way around an unfamiliar repository
Ask a concrete question: how is an order created, where does a price come from, or where does an event go? Gryphon can trace the path through the code and reference the files involved.
Example: understand an unfamiliar billing service
A new teammate needs to change pricing logic in a service with a long history.
- Locate entry points, calculation rules and external dependencies.
- Trace one payment flow in code without making a real payment.
- Map the modules and list questions for the system owner.
What you get
A code guide with file references and a clear starting point for the change.
Where to start
Connect the repository, README and setup instructions. Name the entry point or task you are investigating.
What to ask for
Modules, functions, call order, external dependencies and file references. Ask Gryphon to flag places where the docs disagree with the implementation.
Check your understanding
Trace a small proposed change through the affected modules. Resolve questions with the team and update stale instructions.
Try it on your own task
Open Web and describe the task. Connect Desktop for files and commands on your computer.