repo-context

Scan Git repositories and generate structured context files under ~/.claude/repo-context.

1|Updated May 6, 2023
One-click install
npx skills add https://github.com/TobiasLaross/dotfiles --skill repo-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-context
Source: https://github.com/TobiasLaross/dotfiles/tree/main/agentic/skills/repo-context
Command: npx skills add https://github.com/TobiasLaross/dotfiles --skill repo-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation and updating of per-repo context files to help Claude quickly understand repositories during conversations. It scans two developer directories, generates a standardized context per repository, and stores it under ~/.claude/repo-context/<repo-name>.md, enabling fast retrieval and reduced cognitive load.

Core Features & Use Cases

  • Discover and catalog all Git repositories from ~/Developer/work/ and ~/Developer/personal/.
  • Create or refresh a per-repo context file at ~/.claude/repo-context/<repo-name>.md with a consistent structure.
  • Process repos in batches (up to 10 at a time) with parallel subagents for speed.
  • Update existing context files to reflect code changes, dependencies, and entry points.
  • Use case: you want Claude to summarize a repo's purpose, architecture, and tests before planning changes.

Quick Start

Run /repo-context to scan your developer directories and generate or refresh context files for each repository.

Frequently Asked Questions about repo-context

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

FAQPage Schema
How do I generate context files for multiple Git repositories automatically?

Generating context files for Git repositories automatically involves scanning developer directories and creating structured markdown files per repo, capturing purpose, architecture, and test setup for fast recall.

What is the best way to give Claude Code repository context before planning changes?

The best way to provide Claude Code repository context is creating per-repo context files that summarize the stack, entry points, and architecture into concise markdown files stored under a dedicated context directory.

Can I refresh context files for a specific Git repository without rescanning all directories?

Yes, you can refresh context files for a specific Git repository by providing a repository name argument, which limits processing to that matching repo instead of scanning all developer workspaces.

How does parallel processing work when scanning multiple Git workspaces?

Parallel processing of Git workspaces works by batching unprocessed repositories into chunks of up to 10, running subagents concurrently to generate structured context files simultaneously.

Does this tool require any specific dependencies or components to run?

No, this tool requires no external dependencies or components to run; it operates independently to scan Git repositories and generate standardized markdown context files in the target directory.

What information is included in a generated repository context file?

A generated repository context file includes concise structured information like project Purpose, Language and stack, Architecture, Entry points, and Test setup to provide immediate codebase understanding.