How do I install the Git skill?

Run npx skillmds@latest add lost-rob0t/git 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.

What does the Git skill do?

git, forgejo, github, hosting, remote, fallback, pr, issues It is listed under Coding & Dev Tools on SkillMD.

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 Git?

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.

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

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

Git by lost-rob0t — Agent Skill

Name: Git
Author: lost-rob0t

File contents

Git hosting operations

Goal

Route Git hosting operations (remotes, pull requests, issues, repositories) to the correct host and CLI. The primary host is the self-hosted Forgejo instance git.starintel.actor, used through tea. GitHub is only a fallback.

Host routing

Determine the host from the repository remote URL (git remote -v):
- git.starintel.actor (SSH or HTTPS) -> Forgejo host, use tea.
- github.com -> GitHub fallback, use gh.
- No remote or another host -> ask which host to target before creating anything remote.
If no remote exists yet, prefer creating or linking the repository on git.starintel.actor. Only use GitHub when the operator explicitly asks for GitHub or the Forgejo host is unavailable.
Never duplicate a repository or pull request across hosts. Pick one host per artifact and state the choice.

CLI equivalents

Operation	Forgejo (`tea`)	GitHub fallback (`gh`)
Auth status	`tea login list`	`gh auth status`
Login	`tea login add`	`gh auth login`
Repo view	`tea repo view OWNER/NAME`	`gh repo view OWNER/NAME`
Repo create	`tea repo create NAME`	`gh repo create`
Repo search	`tea repos search NAME`	`gh repo list`
PR list	`tea pr list`	`gh pr list`
PR create	`tea pr create`	`gh pr create`
PR view	`tea pr view NUMBER`	`gh pr view NUMBER`
PR merge	`tea pr merge NUMBER`	`gh pr merge NUMBER`
Issue list	`tea issue list`	`gh issue list`
Issue create	`tea issue create`	`gh issue create`
Issue view	`tea issue view NUMBER`	`gh issue view NUMBER`
Labels	`tea label list` / `tea label create`	`gh label list` / `gh label create`
Releases	`tea release list` / `tea release create`	`gh release list` / `gh release create`

Notes:

tea operates on the login selected with tea login default or the --login flag. Prefer --login <name> for the git.starintel.actor login so the default stays unambiguous.
CI checks differ per host. On Forgejo, query the commit status through the Forgejo API (/api/v1/repos/{owner}/{repo}/commits/{sha}/status) or the Actions run listing; gh pr checks has no tea equivalent.

Rules

Use the host's native CLI for every hosting operation; do not hand-roll API calls when a CLI command exists.
Treat git.starintel.actor as primary. Escalating work to GitHub requires an explicit reason stated to the operator.
Never push tokens, URLs with credentials, or login output containing tokens into logs, commits, or issue text.
Do not create pull requests directly to a protected default branch without the repository's documented Gitflow/checks workflow.
Load the host-specific skill when one exists for the task (for example forgejo-skill-edit or forgejo-repo-bootstrap on Forgejo, their GitHub originals on GitHub).

---name: gitdescription: git, forgejo, github, hosting, remote, fallback, pr, issues---# Git hosting operations## GoalRoute Git hosting operations (remotes, pull requests, issues, repositories)to the correct host and CLI. The primary host is the self-hosted Forgejoinstance `git.starintel.actor`, used through `tea`. GitHub is only afallback.## Host routing1. Determine the host from the repository remote URL (`git remote -v`): - `git.starintel.actor` (SSH or HTTPS) -> Forgejo host, use `tea`. - `github.com` -> GitHub fallback, use `gh`. - No remote or another host -> ask which host to target before creating anything remote.2. If no remote exists yet, prefer creating or linking the repository on `git.starintel.actor`. Only use GitHub when the operator explicitly asks for GitHub or the Forgejo host is unavailable.3. Never duplicate a repository or pull request across hosts. Pick one host per artifact and state the choice.## CLI equivalents| Operation | Forgejo (`tea`) | GitHub fallback (`gh`) ||------------------|----------------------------------|-------------------------------|| Auth status | `tea login list` | `gh auth status` || Login | `tea login add` | `gh auth login` || Repo view | `tea repo view OWNER/NAME` | `gh repo view OWNER/NAME` || Repo create | `tea repo create NAME` | `gh repo create` || Repo search | `tea repos search NAME` | `gh repo list` || PR list | `tea pr list` | `gh pr list` || PR create | `tea pr create` | `gh pr create` || PR view | `tea pr view NUMBER` | `gh pr view NUMBER` || PR merge | `tea pr merge NUMBER` | `gh pr merge NUMBER` || Issue list | `tea issue list` | `gh issue list` || Issue create | `tea issue create` | `gh issue create` || Issue view | `tea issue view NUMBER` | `gh issue view NUMBER` || Labels | `tea label list` / `tea label create` | `gh label list` / `gh label create` || Releases | `tea release list` / `tea release create` | `gh release list` / `gh release create` |Notes:- `tea` operates on the login selected with `tea login default` or the `--login` flag. Prefer `--login <name>` for the `git.starintel.actor` login so the default stays unambiguous.- CI checks differ per host. On Forgejo, query the commit status through the Forgejo API (`/api/v1/repos/{owner}/{repo}/commits/{sha}/status`) or the Actions run listing; `gh pr checks` has no `tea` equivalent.## Rules- Use the host's native CLI for every hosting operation; do not hand-roll API calls when a CLI command exists.- Treat `git.starintel.actor` as primary. Escalating work to GitHub requires an explicit reason stated to the operator.- Never push tokens, URLs with credentials, or login output containing tokens into logs, commits, or issue text.- Do not create pull requests directly to a protected default branch without the repository's documented Gitflow/checks workflow.- Load the host-specific skill when one exists for the task (for example `forgejo-skill-edit` or `forgejo-repo-bootstrap` on Forgejo, their GitHub originals on GitHub).

Frequently asked questions

Git