archibate/dotfiles-opencode / optional-skills/extract-repo
extract-repo
VerifiedDownload GitHub repos as clean source code (no .git history) to WORKDIR. Use when cloning repos for analysis or modification. Not for monorepos.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.4 KB |
| scripts/extract_repo.py | script | 8.1 KB |
SKILL.md
View on GitHub---
name: extract-repo
description: Download GitHub repos as clean source code (no .git history) to WORKDIR. Use when cloning repos for analysis or modification. Not for monorepos.
---
# Extract Repo
Download GitHub repositories as clean source code without git history.
## Usage
Run via subagent:
```bash
uv run .opencode/skill/extract-repo/scripts/extract_repo.py <URL>
```
then `cd` into the extract directory.
## Available Flags
| Flag | Description |
| ----------- | ----------------------------------------- |
| `--help` | Show help message |
| `--dry-run` | Preview what would happen without cloning |
| `--list` | List all managed repos (newest first) |
## Examples
```bash
# Clone a repo
uv run .opencode/skill/extract-repo/scripts/extract_repo.py https://github.com/user/repo
# Works with any GitHub URL (normalizes automatically)
uv run .opencode/skill/extract-repo/scripts/extract_repo.py https://github.com/user/repo/blob/main/README.md
# Preview without cloning
uv run .opencode/skill/extract-repo/scripts/extract_repo.py --dry-run https://github.com/user/repo
# List managed repos
uv run .opencode/skill/extract-repo/scripts/extract_repo.py --list
```
## Notes
- Repos are saved to `WORKDIR/` with a `.extract_repo` marker
- If a repo name already exists, a suffix is added (e.g., `repo-2`)
- The `--remove` flag exists but is interactive; do not use it in automated contexts
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |