sourceatlas

Analyze codebases to identify domains, tech stack, and knowledge gaps.

Updated Feb 5, 2026

Search Tags:#architecture #codebase #patterns #history #overview #kb-learning

Ready to run

npx skills add https://github.com/TomazWang/agent-toolkit --skill sourceatlas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sourceatlas
Source: https://github.com/TomazWang/agent-toolkit/tree/main/plugins/kb-analysis/skills/sourceatlas
Command: npx skills add https://github.com/TomazWang/agent-toolkit --skill sourceatlas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SourceAtlas helps you quickly understand a codebase by revealing the tech stack, architecture, code quality signals, and hotspots, enabling faster KB learning and better planning.

Core Features & Use Cases

Overview: generate a concise project snapshot including tech stack, architecture patterns, and scale.
Pattern: identify common implementation patterns across the codebase.
History: reveal git hotspots and knowledge distribution for team context.
Flow: trace execution paths to understand feature flows.
Dependency: analyze upgrade paths and potential risks.
Speed: provides quick insights by scanning a subset of files.

Quick Start

Navigate to your repository and run /sourceatlas:overview to get a rapid project snapshot.

Frequently Asked Questions about sourceatlas

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a codebase overview to understand architecture and tech stack?▼

To generate a codebase overview, navigate to your repository and run the overview command. It scans a subset of files to produce a concise project snapshot covering tech stack, architecture patterns, and scale.

What is the best way to identify implementation patterns across a codebase?▼

Identifying implementation patterns across a codebase is done using the pattern command, which detects common architectural structures and coding conventions to reveal the main domains and knowledge gaps.

Can I trace execution paths to understand feature flows in a large project?▼

Yes, you can trace execution paths in a large project using the flow command. It analyzes the codebase to map feature flows, enabling rapid overviews and change impact assessment for projects of varying sizes.

How do I analyze git hotspots and knowledge distribution for team context?▼

Analyzing git hotspots and knowledge distribution is accomplished with the history command. It reveals team context and change patterns across the codebase to support knowledge base learning and better planning.

Does the codebase analysis work for assessing dependency upgrade paths and risks?▼

Yes, the dependency analysis command evaluates upgrade paths and potential risks. It assesses change impact by scanning relevant files, providing quick insights for projects of varying sizes.

Do I need to scan the entire repository to get architecture insights?▼

No, you do not need to scan the entire repository to get architecture insights. The analysis provides quick insights by scanning a subset of files, revealing code quality signals and hotspots for faster learning.