# git-remotes

Manage git remote repositories — add/remove/configure remotes, push/pull with safety checks, fetch with pruning, and multi-remote workflows.

## What it does

This skill handles remote operations within the git workflow suite. It manages remote configuration (add, remove, rename), fetch operations with pruning, push operations with force-push safety (`--force-with-lease --force-if-includes`), and pull strategies (fast-forward, rebase, merge). It returns structured results suitable for agent composition.

## Usage

```
/git-remotes
```

Describe your remote operation: add a remote, push, pull, fetch, or configure tracking. The skill will handle the operation with appropriate safety checks and return results.

## Files

| File | Purpose |
|------|---------|
| `SKILL.md` | Skill instructions for agents — force-push gate, dispatch table, return format |
| `references/README.md` | Describes the references directory contents |
| `references/remote-config.md` | Read when adding, removing, renaming, inspecting or re-pointing a remote, or configuring tracking, mirroring, or `set-url` |
| `references/fetch.md` | Read when fetching or pruning remote-tracking refs, or doing a shallow or partial fetch |
| `references/push.md` | Read when pushing branches or tags, writing refspecs, or force-pushing |
| `references/pull.md` | Read when integrating remote changes into the current branch, including the divergence rule |
| `references/sources.md` | Research sources and provenance |

## Composition

Callers that need submodule initialization after a `--recurse-submodules` pull hand off to
`git-submodules`; local-only work (commits, branches, history) belongs to `git-commits`,
`git-branches`, and `git-history`. The `git-workflow` skill routes humans here for any
remote-touching request.