project

Clone external GitHub repositories and link them into psi workspaces.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/thiansit/LuPang --skill project-thiansit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project
Source: https://github.com/thiansit/LuPang/tree/main/.claude/skills/project
Command: npx skills add https://github.com/thiansit/LuPang --skill project-thiansit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ghq, gh, git, bun, and includes scripts (resource) components.

What problem does it solve?

Projects shared as GitHub URLs are often cloned inconsistently, copied into multiple locations, or left unmanaged, making study and contribution workflows messy and hard to track. This Skill enforces a single source-of-truth cloning strategy using ghq plus organized psi symlinks so repositories are discoverable, reversible, and easy to offload.

Core Features & Use Cases

  • Learn (read-only): Clone via ghq and create a psi/learn symlink for study and knowledge extraction.
  • Incubate (active development): Clone or create repos, link into psi/incubate for focused work, and distribute hooks/settings.
  • Search & Find: Local ghq-first search with GitHub API fallback to locate repositories or short slugs.
  • Lifecycle operations: Offload symlinks, reunion (manifesting learnings), spinoff to a new GitHub repo, index manifests to Oracle, and generate git history reports.
  • Use case: When a user says "I want to learn from https://github.com/owner/repo" this Skill clones the source, links it into your knowledge workspace, indexes docs, and records a reunion manifest.

Quick Start

Use the assistant command /project learn https://github.com/owner/repo to clone and link a repository into psi/learn for study.

Frequently Asked Questions about project

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

FAQPage Schema
How do I clone a GitHub repository for study without cluttering my workspace?▼

To clone a GitHub repository for study, use the learn workflow to fetch the repo via ghq and symlink it into a dedicated psi/learn directory. This keeps your knowledge workspace organized and separates read-only study clones from active development.

What's the best way to manage cloned external repositories and track their lifecycle?▼

Managing cloned external repositories is best handled by indexing manifests and using symlinks across ghq and psi workspaces. This approach tracks the repository lifecycle from incubation to offloading, ensuring repos remain discoverable and reversible.

Do I need ghq and gh CLI to use this project cloning workflow?▼

Yes, you need ghq and gh CLI installed to execute this cloning workflow. The Skill relies on ghq for structured local cloning and gh CLI for GitHub API fallback search and repository creation.

Can I search for local repositories and fall back to the GitHub API if not found?▼

Yes, you can search for local repositories with a ghq-first approach that automatically falls back to the GitHub API. This locates repositories or short slugs locally before querying the remote API.

How do I offload a symlinked repository and generate a history report?▼

To offload a symlinked repository, use the lifecycle operation scripts to remove the links and generate a git history report. This process records a reunion manifest to preserve learnings before the project is offloaded.

How does incubating a repository differ from learning?▼

Incubating a repository links it into psi/incubate for active development and distributes hooks and settings, whereas learning clones it as read-only into psi/learn for knowledge extraction. Both use ghq for the initial clone.