git-fork

git-fork

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).

When to use this skill

Use this skill when the user asks to:

• Fork a repo and clone it for contribution work.
• Set up upstream / fork remotes for a repo.
• "Fork X for me", "fork X to org Y", "set up a contributor clone of X".

Do not use this skill when:

• The user only wants to clone a repo (no fork). Use git clone directly.
• The user only wants to fork on GitHub without a local clone. Use gh repo fork directly.

How to invoke

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:

1. Clones <repo> into ./<directory> with the original as upstream. The local default branch tracks upstream/<default>.
2. Forks <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.
3. Applies repo settings to the fork via gh repo edit (skipped if the fork step was skipped). Defaults:
   • delete-branch-on-merge=true
   • enable-wiki=false
   • enable-projects=false
   • enable-merge-commit=false
   • enable-squash-merge=false
4. Adds a fork remote pointing at <account>/<name>.

The script refuses to overwrite an existing ./<directory>.

Configuration: ~/.agitentic

Fork 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.

Example

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.

Requirements

• git
• gh (GitHub CLI), authenticated. The skill uses gh api user --jq .login to discover the default account and gh repo fork to create the fork.