extract-repo

Download GitHub repositories as clean working copies without git history.

103|21|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/archibate/dotfiles-opencode --skill extract-repo-archibate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: extract-repo
Source: https://github.com/archibate/dotfiles-opencode/tree/main/optional-skills/extract-repo
Command: npx skills add https://github.com/archibate/dotfiles-opencode --skill extract-repo-archibate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rich, questionary, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the hassle of working with GitHub repositories that include git history, so you can analyze or modify only the source code without the extra metadata.

Core Features & Use Cases

  • Shallow, clean cloning: Downloads a GitHub repo as source code without the full .git history.
  • Automatic URL normalization: Accepts typical GitHub URLs (including /blob/...) and resolves them to the repo root.
  • Managed extraction workspace: Stores extracted repos under a dedicated WORKDIR with conflict-safe naming and listing/removal support.

Quick Start

Run the Skill’s script to extract a target repository into the workspace for subsequent editing or analysis.

Frequently Asked Questions about extract-repo

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

FAQPage Schema
How do I download a GitHub repo as source code without git history?

Clone a GitHub repository without git history by performing a shallow clone into a workspace and removing the `.git` directory. This extracts clean source files for codebase inspection, patching, refactoring, and security review.

Can I extract source code directly from a GitHub blob URL?

Yes, extracting source from a GitHub blob URL is supported. The tool automatically normalizes typical GitHub URLs, including blob links, resolving them to the repository root before downloading the clean working copy.

What is the best way to manage multiple extracted GitHub repositories for local analysis?

Store extracted GitHub repositories under a dedicated workspace with conflict-safe naming. This managed extraction workspace supports listing and optional interactive removal of repos during local codebase inspection.

Does shallow cloning a GitHub repository remove all git metadata?

Shallow cloning a GitHub repository removes git metadata. By performing a shallow clone into a workdir and deleting the `.git` folder, you get a clean working copy without the extra metadata.

When should I not use a clean source code extraction for a GitHub repo?

Avoid clean source code extraction when you need to analyze commit logs, track git history, or manage branch merges. This approach strictly provides current working files without the repository's historical metadata.