You just cloned a repo. It’s 15,000 lines of code, there’s no documentation, and the README was last updated three years ago. Where do you even start? That’s a situation almost every developer has faced — whether you’re joining a new team or diving into an open-source project for the first time. Understanding how a codebase works can take hours, sometimes days, before you feel confident making changes. But with the rise of AI coding assistants, that process is getting a lot easier. Tools powered by large language models can now read your codebase, understand how it’s structured, and even summarize what each folder or file is for. What used to be a slow, manual process can now take just a few minutes. AI coding assistants read In this walkthrough, I’ll show you how to do it using Kilocode inside VS Code, specifically leveraging its feature called Memory Bank. You can use the same concept with other assistants that offer project memory or context features like Cline, Roo Code or Claude Code. Kilocode VS Code Memory Bank Cline, Roo Code Claude Code. Step-by-Step: Understanding a Codebase with Kilocode Clone the Repository
Start by cloning the repository you want to analyze:
git clone https://github.com/your-project.git 

This could be a company project, an open-source repo, or even one of your old codebases that you want to revisit.


Install Kilocode in VS Code
If you haven't used Kilocode before, install it from the marketplace in VS Code (if you're using VS Code).
If you're not using VS Code, then please check other installation guide here: Kilocode Installation Guide
Once it's set up, open your cloned project in VS Code. Clone the Repository
Start by cloning the repository you want to analyze:
git clone https://github.com/your-project.git 

This could be a company project, an open-source repo, or even one of your old codebases that you want to revisit. Clone the Repository Clone the Repository Start by cloning the repository you want to analyze: git clone https://github.com/your-project.git git clone https://github.com/your-project.git This could be a company project, an open-source repo, or even one of your old codebases that you want to revisit. Install Kilocode in VS Code
If you haven't used Kilocode before, install it from the marketplace in VS Code (if you're using VS Code).
If you're not using VS Code, then please check other installation guide here: Kilocode Installation Guide
Once it's set up, open your cloned project in VS Code. Install Kilocode in VS Code Install Kilocode in VS Code If you haven't used Kilocode before, install it from the marketplace in VS Code (if you're using VS Code). If you're not using VS Code, then please check other installation guide here: Kilocode Installation Guide Kilocode Installation Guide Once it's set up, open your cloned project in VS Code. The guides below can be found here as well: Setting up Memory Bank The guides below can be found here as well: Setting up Memory Bank Setting up Memory Bank Set Up the Memory Bank
The Memory Bank is what allows Kilocode to “remember” and understand your project context.
In your project directory, create:
.kilocode/rules/memory-bank/

Inside that folder, add a new file named brief.md and write a short, high-level overview of the project: what it does and why it exists.
Next, create another file called:
.kilocode/rules/memory-bank-instructions.md

and paste the content from this document. This helps guide Kilocode’s analysis process.


Initialize the Memory Bank
Now let’s get Kilocode to analyze the project:

Switch Kilocode to Architect mode.
Make sure you’re using a high-quality model (avoid lightweight ones).
Ask Kilocode to “initialize memory bank.”
Wait while it analyzes your entire codebase and builds the documentation.
Review the generated files to ensure the descriptions make sense. Edit or refine them as needed.

For reference, here’s the full guide: Getting started with memory bank


Review the Generated Docs
Once the analysis is complete, Kilocode will create several Markdown files describing your project. These include:

product.md — Explains why the project exists, the problems it solves, and the intended user experience.
context.md — Tracks current work, recent changes, and next steps for development.
architecture.md — Maps out the system architecture, design patterns, and key component relationships.
tech.md — Lists frameworks, dependencies, environment setup, and tool configurations.

These files effectively serve as auto-generated documentation — giving you a complete picture of the project’s structure and purpose in minutes.
Focus especially on architecture.md and tech.md, since they provide the clearest view of how the system works and what technologies it relies on. Set Up the Memory Bank
The Memory Bank is what allows Kilocode to “remember” and understand your project context.
In your project directory, create:
.kilocode/rules/memory-bank/

Inside that folder, add a new file named brief.md and write a short, high-level overview of the project: what it does and why it exists.
Next, create another file called:
.kilocode/rules/memory-bank-instructions.md

and paste the content from this document. This helps guide Kilocode’s analysis process. Set Up the Memory Bank Set Up the Memory Bank The Memory Bank is what allows Kilocode to “remember” and understand your project context. Memory Bank In your project directory, create: .kilocode/rules/memory-bank/ .kilocode/rules/memory-bank/ Inside that folder, add a new file named brief.md and write a short, high-level overview of the project: what it does and why it exists. brief.md Next, create another file called: .kilocode/rules/memory-bank-instructions.md .kilocode/rules/memory-bank-instructions.md and paste the content from this document. This helps guide Kilocode’s analysis process. this document Initialize the Memory Bank
Now let’s get Kilocode to analyze the project:

Switch Kilocode to Architect mode.
Make sure you’re using a high-quality model (avoid lightweight ones).
Ask Kilocode to “initialize memory bank.”
Wait while it analyzes your entire codebase and builds the documentation.
Review the generated files to ensure the descriptions make sense. Edit or refine them as needed.

For reference, here’s the full guide: Getting started with memory bank Initialize the Memory Bank Initialize the Memory Bank Now let’s get Kilocode to analyze the project: Switch Kilocode to Architect mode.
Make sure you’re using a high-quality model (avoid lightweight ones).
Ask Kilocode to “initialize memory bank.”
Wait while it analyzes your entire codebase and builds the documentation.
Review the generated files to ensure the descriptions make sense. Edit or refine them as needed. Switch Kilocode to Architect mode. Architect mode Make sure you’re using a high-quality model (avoid lightweight ones). Ask Kilocode to “initialize memory bank.” “initialize memory bank.” Wait while it analyzes your entire codebase and builds the documentation. Review the generated files to ensure the descriptions make sense. Edit or refine them as needed. For reference, here’s the full guide: Getting started with memory bank Getting started with memory bank Review the Generated Docs
Once the analysis is complete, Kilocode will create several Markdown files describing your project. These include:

product.md — Explains why the project exists, the problems it solves, and the intended user experience.
context.md — Tracks current work, recent changes, and next steps for development.
architecture.md — Maps out the system architecture, design patterns, and key component relationships.
tech.md — Lists frameworks, dependencies, environment setup, and tool configurations.

These files effectively serve as auto-generated documentation — giving you a complete picture of the project’s structure and purpose in minutes.
Focus especially on architecture.md and tech.md, since they provide the clearest view of how the system works and what technologies it relies on. Review the Generated Docs Review the Generated Docs Once the analysis is complete, Kilocode will create several Markdown files describing your project. These include: product.md — Explains why the project exists, the problems it solves, and the intended user experience.
context.md — Tracks current work, recent changes, and next steps for development.
architecture.md — Maps out the system architecture, design patterns, and key component relationships.
tech.md — Lists frameworks, dependencies, environment setup, and tool configurations. product.md — Explains why the project exists, the problems it solves, and the intended user experience. product.md context.md — Tracks current work, recent changes, and next steps for development. context.md architecture.md — Maps out the system architecture, design patterns, and key component relationships. architecture.md tech.md — Lists frameworks, dependencies, environment setup, and tool configurations. tech.md These files effectively serve as auto-generated documentation — giving you a complete picture of the project’s structure and purpose in minutes. auto-generated documentation Focus especially on architecture.md and tech.md, since they provide the clearest view of how the system works and what technologies it relies on. architecture.md tech.md Results Example I used Nextcloud Deck as an example project for this tutorial. Nextcloud Deck You can check the GitHub repository here: https://github.com/nextcloud/deck https://github.com/nextcloud/deck What you’re seeing above are examples of the Memory Bank files generated by Kilocode, including documentation like architecture.md and tech.md. Memory Bank files architecture.md tech.md Each file provides structured insights into the codebase and together; these files give you a clear overview of the project, the kind of understanding that would normally take hours to piece together manually. Instead of scrolling through endless directories or guessing at folder names, you instantly see how the codebase is organized and what each part does. In just a few minutes, you’ve gone from staring at an unfamiliar repo to understanding its logic, structure, and purpose; without digging through every file by hand. understanding its logic, structure, and purpose; without digging through every file by hand. What used to take hours of manual exploration; tracing dependencies, scanning files, and guessing architecture, can now be done in minutes with AI assistance. Tools like Kilocode don’t just summarize code; they transform how we onboard, document, and collaborate on software projects. transform how we onboard, document, and collaborate By combining structured analysis with natural-language explanations, AI coding assistants let developers spend less time figuring out the codebase and more time improving it. Whether you’re joining a new team, contributing to open source, or auditing an old project, this approach makes understanding large codebases faster, clearer, and far less painful. figuring out improving Conclusion The rise of AI (and especially large language models) has opened up countless ways to improve how we code and collaborate. One of the most underrated use cases is accelerating code comprehension — turning a time-consuming onboarding process into a quick, structured overview. accelerating code comprehension AI coding assistants aren’t here to replace developers, but they can dramatically boost our productivity. By offloading repetitive cognitive tasks like summarizing code or tracing architecture, developers can spend more time doing what matters: designing, building, and solving real problems. dramatically boost our productivity In an era where new AI tools appear every week, it’s worth keeping an open mind and experimenting. You might discover that your next favorite “teammate” is an AI agent that helps you understand codebases faster than ever before. Let’s keep the conversation going! I share daily thoughts, resources, and questions on X about AI, tech, and building in public. Join me here 👉 @jmstdy95 Let’s keep the conversation going! I share daily thoughts, resources, and questions on X about AI, tech, and building in public. Join me here 👉 @jmstdy95 @jmstdy95 @jmstdy95

This story contains new, firsthand information uncovered by the writer.

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

The is an opinion piece based on the author’s POV and does not necessarily reflect the views of HackerNoon.

This story contains AI-generated text. The author has used AI either for research, to generate outlines, or write the text itself. 

How to Understand Any Codebase in 5 Minutes Using an AI Coding Assistant

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

A Quick Guide to Quantization for LLMs

The Noonification: How Often Do NFTs Pass The Howey Test? (1/13/2023)

Darwin's Hybrid Intelligence to Align AI & Human Goals for Startups & VCs

The Noonification: White Man (11/26/2022)

The Noonification: The Metaverse is a Sh*tshow (11/2/2022)

A Quick Guide to Quantization for LLMs

The Noonification: How Often Do NFTs Pass The Howey Test? (1/13/2023)

Darwin's Hybrid Intelligence to Align AI & Human Goals for Startups & VCs

The Noonification: White Man (11/26/2022)

The Noonification: The Metaverse is a Sh*tshow (11/2/2022)

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps