GitHub Forker

Fork GitHub repositories extracted from text or images. You need GITHUB_TOKEN set in the environment with repo permissions.

What you do

1. Extract all GitHub repository URLs from the input (text, image, or both)
2. Fork each repository via the GitHub API
3. Star the original repository after a successful fork
4. Report results clearly

Step 1: Extract GitHub URLs

From text

Scan the input for patterns matching:

• https://github.com/{owner}/{repo} (with or without trailing slash, path, or fragment)
• github.com/{owner}/{repo} (without scheme)
• {owner}/{repo} only when context makes it clearly a GitHub repo

Normalize each match to the canonical form: https://github.com/{owner}/{repo} Strip any extra path segments — you only need owner and repo name.

From images

When the user provides an image (screenshot, photo, diagram), use your vision capabilities to read the image and identify any GitHub URLs or repo references visible in it. Apply the same extraction rules as above to whatever text you find.

Truncated URLs

URLs are often cut off in screenshots or social media previews, like:

• github.com/openchamber/op...
• github.com/some-owner/proj…

When you detect a truncated URL (ends with ... or …, or the repo name is clearly incomplete):

1. Search GitHub for matching repos:

   curl -s -L \
     -H "Authorization: Bearer $GITHUB_TOKEN" \
     -H "Accept: application/vnd.github+json" \
     "https://api.github.com/search/repositories?q={owner}/{partial}+in:full_name&per_page=5"
   

   Use whatever partial info you have — owner + partial repo name is ideal; owner alone works too.

2. Use context to pick the best match. Look at surrounding text, tweet content, project name mentioned, description keywords, and star count. If one result stands out clearly:

   • The repo name starts with the visible partial (e.g. op... → openchamber matches)
   • The description aligns with what the user said (e.g. "UI真好" → pick the UI-focused one)
   • It has significantly more stars than the others

   If you're confident, proceed directly and tell the user your reasoning:

   "github.com/openchamber/op..." → inferred openchamber/openchamber ⭐1.5k (Desktop UI for OpenCode, matches context "UI真好")
   

3. Ask the user only when genuinely uncertain — when multiple results are plausible and context doesn't help distinguish them:

   Found truncated URL "github.com/foo/bar..." — which repo did you mean?
   1. foo/barista ⭐420 — Coffee shop POS system
   2. foo/baroque ⭐38 — Baroque music generator
   Enter number (or 0 to skip):
   

   Never fork a truncated URL without either a confident inference or explicit user confirmation.

Step 2: Fork via GitHub API

For each unique {owner}/{repo} pair, call the fork endpoint: