gitingest

Fetch GitHub repositories and output structured summaries to docs/reference.

9|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/ivy/dotfiles --skill gitingest
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitingest
Source: https://github.com/ivy/dotfiles/tree/main/home/dot_claude/skills/gitingest
Command: npx skills add https://github.com/ivy/dotfiles --skill gitingest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fetch and contextualize a GitHub repository for future reference by producing a structured, searchable summary of the repo's purpose, key files, and context.

Core Features & Use Cases

  • Contextualizes repository contents into a concise summary including repo name, purpose, and notable files.
  • Accepts input as a full URL, user/repo, or a canonical repo name; supports optional filters and branch selection; can operate on private repos with a GitHub PAT.
  • Outputs a deterministic artifact to docs/reference/<owner>-<repo>.txt and reports the repo name, purpose, file location, and filters applied.

Quick Start

Provide a GitHub URL or user/repo to generate a contextual repository summary in the docs/reference directory.

Frequently Asked Questions about gitingest

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

FAQPage Schema
How do I generate a text summary of a GitHub repository for quick context?

To generate a GitHub repository summary, provide a full URL, user/repo, or canonical name. The tool contextualizes repo contents and outputs a structured text file summarizing the repo name, purpose, and notable files.

Can I fetch and summarize a private GitHub repository?

Yes, you can fetch and summarize a private GitHub repository by supplying a GitHub Personal Access Token (PAT). This allows the CLI to authenticate and access private repository contents for contextualization.

How do I contextualize a specific branch of a GitHub repo?

To contextualize a specific GitHub repo branch, include the branch selection option in your input. The tool supports optional branch targeting to fetch and summarize repository contents from non-default branches.

Does the repository context tool support filtering specific files or directories?

Yes, the repository context tool supports optional filters. You can apply filters to narrow the contextualization scope, ensuring the output summary file only includes the file structure and content you specifically need.

Where does the fetched GitHub repository context get saved?

The fetched GitHub repository context gets saved as a deterministic artifact at docs/reference/<owner>-<repo>.txt. This file contains the repo name, purpose, notable files, and applied filters for future reference.