# Understanding someone else’s code

> Find your way around an unfamiliar project — from a quick question to a full audit, read-only.

Use case

# Understanding someone else’s code

You have joined an unfamiliar project and need to get up to speed fast — without hours of reading and without risking breaking anything.

[Connect a repository](https://buff.systems/app) [All use cases](https://buff.systems/en/use-cases)

Situation

## Find your way around an unfamiliar project — from a quick question to a full audit, read-only.

What gets in the way

- You have joined an unfamiliar project and need to get up to speed fast.
- You need an answer about one specific place in the code, not an hour of reading.
- You want to test a hypothesis without changing anything.
- You need to know what changed in a branch, or the status of a task.

Solution 01

## “Ask” — a quick answer about the code

Ask a question — Buff reads the source code, as well as connected trackers and documents, and answers with links to specific files, changing nothing. “Where is the /search response built?”, “What changed in the branch?”, “What is the status of task No. …?” — a quick way to test a hypothesis and find the right place. No development project is needed for this: it works with any connected repository.

[About “Ask”](https://buff.systems/en/docs/ask)

**“Ask” — a quick answer about the code**

← scroll the frame →

“Ask”: an answer about the code with links to specific files.

Solution 02

## Audit — the picture of the whole project

When you need the overall picture rather than a precise answer, an audit reviews the whole project: domains, architecture, dependencies, behaviour and risk areas. The ready sections explain the structure without reading the code line by line.

[About audits](https://buff.systems/en/docs/audits)

**Audit — the picture of the whole project**

← scroll the frame →

Audit: sections on code, architecture and risks.

Solution 03

## Deep research — when you need an analysis

If the question is complex and needs working through rather than a chat answer, deep research by two agents prepares a verified document on your code and connected knowledge sources, with options and reasoning.

[About research](https://buff.systems/en/docs/research)

**Deep research — when you need an analysis**

← scroll the frame →

Deep research: a verified analysis of the code.

Outcome

You have understood the project — from one specific place to the overall picture — and changed nothing in it.

The first step changes nothing in the code

## Start with a question about your project

Connect a repository and ask the system how your code is built: it reads the source code and answers in minutes, changing nothing. A starting balance is provided to try it out.

[Connect a repository](https://buff.systems/app) [Write to us](mailto:info@buff.systems)

Companies and sole traders can pay by bank transfer and receive closing documents