From agitentic
Fork a GitHub repository and clone it locally with the contributor-style two-remote layout — `upstream` points at the original repo (local default branch tracks it) and `fork` points at the fork. Also applies sensible repo settings to the fork (`delete_branch_on_merge=true`, wiki/projects/merge-commit/squash-merge disabled), overridable via `~/.agitentic`. Use when the user asks to fork a repo, set up a contributor clone, or wire up upstream + fork remotes for a repo they're about to contribute to. Keywords - fork, clone, upstream, contribute, set up remotes, github fork.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agitentic:git-forkThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fork a GitHub repository, clone the upstream locally, and configure two
Fork a GitHub repository, clone the upstream locally, and configure two remotes so the workflow is ready for contributions:
upstream → the original repository. The local default branch tracks
upstream/<default>.fork → the user's fork (or a specified org's fork).Use this skill when the user asks to:
upstream / fork remotes for a repo.Do not use this skill when:
git clone directly.gh repo fork directly.Run the bundled script:
scripts/git-fork <repo> [account] [directory]
<repo> (required) — the repository to fork. Accepts owner/name or
any GitHub HTTPS / SSH URL (https://github.com/owner/name,
[email protected]:owner/name.git, etc.).[account] (optional) — the destination owner for the fork. Defaults
to the currently authenticated gh user. Pass "" to use the
default while still specifying [directory].[directory] (optional) — local directory to clone into. Defaults
to the repo name.The script:
<repo> into ./<directory> with the original as upstream.
The local default branch tracks upstream/<default>.<repo> to <account>/<name> via gh repo fork. If
<account> is the upstream owner, the fork step is skipped. If
<account> is not the authenticated user, --org <account> is used,
so the caller must have permission to fork into that org.gh repo edit (skipped if the
fork step was skipped). Defaults:
delete-branch-on-merge=trueenable-wiki=falseenable-projects=falseenable-merge-commit=falseenable-squash-merge=falsefork remote pointing at <account>/<name>.The script refuses to overwrite an existing ./<directory>.
~/.agitenticFork repo settings are read from a [fork] section in ~/.agitentic
(or $AGITENTIC_CONFIG if set). The file uses git config format:
[fork]
delete-branch-on-merge = true
enable-wiki = false
enable-projects = false
enable-merge-commit = false
enable-squash-merge = false
enable-rebase-merge = true
Keys map directly to gh repo edit flags (the leading -- is added
by the script). Values must be valid for the corresponding flag —
booleans (true/false) for the flags above; strings for flags like
description. Built-in defaults apply for any key not in the file, so
users can override individual settings without re-specifying the rest.
If ~/.agitentic doesn't exist, the built-in defaults are used.
User: "Fork brevdev/brev-cli for me"
Run, from the directory where the user wants the clone to land:
scripts/git-fork brevdev/brev-cli
User: "Fork it into the acme org"
scripts/git-fork brevdev/brev-cli acme
User: "Fork brevdev/brev-cli into ~/work/brev"
cd ~/work && scripts/git-fork brevdev/brev-cli "" brev
After the script returns, show the user git -C <directory> remote -v
so the two-remote layout is visible.
gitgh (GitHub CLI), authenticated. The skill uses gh api user --jq .login to discover the default account and gh repo fork to create
the fork.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub brycelelbach/agitentic --plugin agitentic