Supported interfaces
What you can do
With Codebase Wisdom, you can:- Understand relationships between repositories, services, and components.
- Analyze the impact of proposed changes before writing code.
- Explore previous pull requests and implementation history.
- Inspect the current state of branches, commits, and pull requests.
- Investigate regressions and identify the changes that introduced them.
- Build context quickly when working in an unfamiliar part of the codebase.
Common use cases
Understand your architecture
Explore how repositories, services, and components relate to one another without manually tracing code. Use it to:- Identify which services call a specific API.
- Understand dependencies between repositories.
- Discover how data flows through your system.
- Learn how an unfamiliar feature is implemented.
- How does authentication work in the payments service?
- Which services depend on the billing API?
- How does a checkout request flow through the system?
Analyze the impact of a change
Before modifying code, understand what the change could affect across your organization. Use it to:- Identify dependent repositories.
- Evaluate the scope of a change.
- Reduce the risk of introducing breaking changes.
- Plan work across multiple repositories.
- What would break if I changed this interface?
- Which repositories depend on this library?
- What services would be affected by changing this API?
Learn from previous implementations
Discover how similar problems were solved in the past by searching your pull request history. Use it to:- Find previous implementations.
- Understand design decisions.
- Reuse existing patterns.
- Avoid duplicating work.
- How did we implement rate limiting?
- When was OAuth added?
- Who introduced this feature?
Understand current development
Get visibility into your current development activity without leaving your workflow. Use it to:- Review open pull requests.
- Check active branches.
- See recent commits.
- Determine whether work is already in progress.
- What pull requests are currently open?
- Has anyone started implementing feature flags?
- What recently changed in the billing service?
Investigate regressions
Quickly identify the changes that may have introduced a bug or unexpected behavior. Use it to:- Trace regressions to recent changes.
- Understand what changed before an issue appeared.
- Correlate Git history with affected components.
- Speed up root cause analysis.
- Why did the checkout start failing last week?
- Which recent changes affected authentication?
- What changed before this test began failing?
Onboard to a new codebase
Build context quickly when joining a new project or working in an unfamiliar area. Use it to:- Understand how repositories fit together.
- Learn the architecture of a service.
- Explore historical development.
- Find relevant implementation examples.
- Explain the payments architecture.
- How are these repositories connected?
- Where should I start if I’m working on authentication?