How do I install the Skogai Gita skill?

Run npx skillmds@latest add skogai/skogai-gita in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skogai Gita safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skogai Gita?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skogai Gita free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Skogai Gita?

skogai (@skogai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skogai Gita by skogai — Agent Skill

Name: Skogai Gita
Author: skogai

Skogai Gita

Multi-repo git management with the gita CLI. Use when checking status across multiple repositories, fetching/pulling all repos at once, running git commands across repo groups, or when the user mentions gita, repo groups, or wants a bird's-eye view of their git repositories. Also use when working with repos in ~/claude/ or ~/.local/src/ and you need to understand what's there or operate on them in bulk.

skogai Updated Sep 17, 2026

File contents

gita manages multiple git repos from any working directory. two core capabilities:

dashboard — see status of all repos (or a group) side by side
delegation — run git commands against specific repos without cd-ing

all repos live in ~/.local/src/. symlinks in ~/claude/ point there. gita tracks 18 repos total.

groups scope operations. current setup:

group	repos	notes
`src`	all 17 repos in `~/.local/src/`	aichat, argc, argc-completions, claude-memory, cli, docs, dot-skogai, episodic-memory, everything-claude-code, get-shit-done, gita, gptme-contrib, marketplace, nelson, skogterm, small-hours, worktrunk
`develop`	skogix/claude	the `~/claude/` workspace repo

context is currently set to src (stored in ~/.config/gita/src.context).

skogix/claude is the auto-prefixed name for ~/claude/ — gita prefixes with the parent dir to avoid collision with any repo named claude.

status and overview

gita ll                    # all repos (or context group)
gita ll src                # just ~/.local/src/ repos
gita st                    # short status

ll output shows: repo name, branch, dirty indicators, last commit, age, path, tracking branch.

dirty indicators: * unstaged, + staged, $ stashed, ? untracked, ↑ ahead, ↓ behind.

targeted git commands

gita super <repo> <git-command>
gita super claude-memory pull
gita super nelson log --oneline -5

bulk operations

gita fetch                   # fetch all (or context group)
gita fetch src               # fetch src group
gita pull src                # pull all src repos

shell commands

gita shell <repo> <shell-command>
gita shell docs "ls -la"

context (default group)

gita context src             # set default — all commands scope to this
gita context none            # clear context

repo management

gita ls                      # list all repo names
gita ls <repo>               # show repo path
gita add /path/to/repo       # register
gita rm <repo>               # unregister
gita group ls                # list groups
gita group add -n <name> <repo1> <repo2> ...
gita group rm <name>
gita rename <old> <new>

group names cannot collide with repo names.

freeze and restore

gita freeze                           # capture full state (URLs, paths, branches)
gita freeze > freeze.csv              # save to file
gita clone -f freeze.csv -p           # restore from freeze

-p (preserve-path) is required to clone into original paths. without it, repos clone into cwd.

morning check — fetch and see what's dirty or behind:

gita fetch && gita ll

find uncommitted work — look for *, +, ? indicators:

gita ll

add a new project repo:

gita add ~/.local/src/new-repo
gita group add -n src <all-existing-src-repos> new-repo

config at ~/.config/gita/ — version-controlled copy at skills/gita/config/:

file	purpose
`repos.csv`	registered repos (path, name, flags)
`groups.csv`	group definitions
`info.csv`	display column config
`src.context`	current context setting
`freeze.csv`	full state snapshot for backup/restore

the skills/gita/config/ directory is the version-controlled source. sync to ~/.config/gita/ as needed.

---name: skogai-gitadescription: Multi-repo git management with the gita CLI. Use when checking status across multiple repositories, fetching/pulling all repos at once, running git commands across repo groups, or when the user mentions gita, repo groups, or wants a bird's-eye view of their git repositories. Also use when working with repos in ~/claude/ or ~/.local/src/ and you need to understand what's there or operate on them in bulk.---<what_is_this>gita manages multiple git repos from any working directory. two core capabilities:1. **dashboard** — see status of all repos (or a group) side by side2. **delegation** — run git commands against specific repos without cd-ingall repos live in `~/.local/src/`. symlinks in `~/claude/` point there. gita tracks 18 repos total.</what_is_this><groups>groups scope operations. current setup:| group | repos | notes ||-------|-------|-------|| `src` | all 17 repos in `~/.local/src/` | aichat, argc, argc-completions, claude-memory, cli, docs, dot-skogai, episodic-memory, everything-claude-code, get-shit-done, gita, gptme-contrib, marketplace, nelson, skogterm, small-hours, worktrunk || `develop` | skogix/claude | the `~/claude/` workspace repo |context is currently set to `src` (stored in `~/.config/gita/src.context`).`skogix/claude` is the auto-prefixed name for `~/claude/` — gita prefixes with the parent dir to avoid collision with any repo named `claude`.</groups><commands>## status and overview```bashgita ll # all repos (or context group)gita ll src # just ~/.local/src/ reposgita st # short status````ll` output shows: repo name, branch, dirty indicators, last commit, age, path, tracking branch.dirty indicators: `*` unstaged, `+` staged, `$` stashed, `?` untracked, `↑` ahead, `↓` behind.## targeted git commands```bashgita super <repo> <git-command>gita super claude-memory pullgita super nelson log --oneline -5```## bulk operations```bashgita fetch # fetch all (or context group)gita fetch src # fetch src groupgita pull src # pull all src repos```## shell commands```bashgita shell <repo> <shell-command>gita shell docs "ls -la"```## context (default group)```bashgita context src # set default — all commands scope to thisgita context none # clear context```## repo management```bashgita ls # list all repo namesgita ls <repo> # show repo pathgita add /path/to/repo # registergita rm <repo> # unregistergita group ls # list groupsgita group add -n <name> <repo1> <repo2> ...gita group rm <name>gita rename <old> <new>```group names cannot collide with repo names.## freeze and restore```bashgita freeze # capture full state (URLs, paths, branches)gita freeze > freeze.csv # save to filegita clone -f freeze.csv -p # restore from freeze````-p` (preserve-path) is required to clone into original paths. without it, repos clone into cwd.</commands><workflows>**morning check** — fetch and see what's dirty or behind:```bashgita fetch && gita ll```**find uncommitted work** — look for `*`, `+`, `?` indicators:```bashgita ll```**add a new project repo:**```bashgita add ~/.local/src/new-repogita group add -n src <all-existing-src-repos> new-repo```</workflows><config>config at `~/.config/gita/` — version-controlled copy at `skills/gita/config/`:| file | purpose ||------|---------|| `repos.csv` | registered repos (path, name, flags) || `groups.csv` | group definitions || `info.csv` | display column config || `src.context` | current context setting || `freeze.csv` | full state snapshot for backup/restore |the `skills/gita/config/` directory is the version-controlled source. sync to `~/.config/gita/` as needed.</config>

Frequently asked questions