How do I install the Git Workflow skill?

Run npx skillmds@latest add tomevault-io/git-workflow-46 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 Git Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Git Workflow?

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 Git Workflow free to use?

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

Who published Git Workflow?

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

Git Workflow by tomevault-io — Agent Skill

Name: Git Workflow
Author: tomevault-io

Git Workflow

Run git status / log / diff and list pull requests for the session's repo via the opendray gateway. Use whenever the user asks about "what's changed", "status", "diff", "open PRs", or wants to commit / push. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

git-workflow

The opendray gateway exposes read-only git inspection endpoints backed by the git binary in the session's cwd, plus PR listing across configured hosts (GitHub, Gitea, GitLab). Use them instead of shelling out to git directly when you want structured output that's easy to summarise back to the user — falls back to plain git for anything not covered.

When to use

User asks "what's changed", "status", "what files did I touch"
User wants to see a recent commit, a file's diff, or a PR list
Before committing, to verify staged vs unstaged
Before opening a PR, to check the diff against HEAD or origin

For destructive ops (commit, push, branch, rebase, …) keep using the plain git CLI — those are not exposed via the gateway and are safer to run with the user's explicit confirmation.

Endpoints (gateway runs at http://127.0.0.1:8770 by default)

All endpoints accept path=<absolute cwd> and require the admin session token. Inside an opendray-spawned session, you can rely on the local gateway being reachable; curl -s works.

GET /api/v1/git/status?path=<dir>           → branch, ahead/behind, files
GET /api/v1/git/log?path=<dir>&n=20         → recent commits
GET /api/v1/git/diff?path=<dir>&scope=all   → unified diff (HEAD)
GET /api/v1/git/diff?path=<dir>&scope=staged&file=<rel>
GET /api/v1/git/show?path=<dir>&hash=<sha>  → commit + patch
GET /api/v1/git/remote?path=<dir>           → owner/repo + token state
GET /api/v1/git/prs?path=<dir>&state=open   → list pull requests

Most of the time the plain CLI is faster and the user expects familiar git output. Reach for the gateway endpoints when:

you want to surface a structured PR list (no gh/tea setup needed)
the user wants you to summarise a long diff without dumping all of it into the chat — fetch the JSON, then paraphrase

Patterns

Quick status summary

git -C "$PWD" status --short
git -C "$PWD" log --oneline -5

Review the working tree before committing

git diff --stat HEAD
git diff --cached  # staged
git diff           # unstaged

Show recent open PRs without per-CLI auth

curl -s "http://127.0.0.1:8770/api/v1/git/prs?path=$PWD&state=open" \
  | jq '.prs[] | {number, title, author, head, base}'

If need_token: true comes back, tell the user to add a token in the opendray Plugins page (Git hosts section) for the matching host.

Conventions

This repo uses conventional commits: <type>: <description> where type ∈ {feat, fix, refactor, docs, test, chore, perf, ci}.

Branch naming: <type>/<short-slug> (e.g. feat/notes-vault).

PRs should:

have a 1-3 sentence summary at the top
include a Test Plan checklist
reference any related issue / decision note in projects/<basename>/decisions/

Safety

Never run destructive git ops without confirming the working tree state and asking the user
For force-push, rebase main, branch -D — always pause and confirm
Read-only endpoints are safe to call freely; PR listing hits remote APIs (GitHub/Gitea/GitLab), which counts against rate limits

Source: Opendray/opendray — distributed by TomeVault.

---name: git-workflow-46description: Run git status / log / diff and list pull requests for the session's repo via the opendray gateway. Use whenever the user asks about "what's changed", "status", "diff", "open PRs", or wants to commit / push. Use when this capability is needed.---# git-workflowThe opendray gateway exposes read-only git inspection endpointsbacked by the `git` binary in the session's cwd, plus PR listingacross configured hosts (GitHub, Gitea, GitLab). Use them instead ofshelling out to `git` directly when you want structured output that'seasy to summarise back to the user — falls back to plain `git` foranything not covered.## When to use- User asks "what's changed", "status", "what files did I touch"- User wants to see a recent commit, a file's diff, or a PR list- Before committing, to verify staged vs unstaged- Before opening a PR, to check the diff against `HEAD` or originFor destructive ops (commit, push, branch, rebase, …) keep using theplain `git` CLI — those are not exposed via the gateway and are saferto run with the user's explicit confirmation.## Endpoints (gateway runs at http://127.0.0.1:8770 by default)All endpoints accept `path=<absolute cwd>` and require the adminsession token. Inside an opendray-spawned session, you can rely on thelocal gateway being reachable; `curl -s` works.```GET /api/v1/git/status?path=<dir> → branch, ahead/behind, filesGET /api/v1/git/log?path=<dir>&n=20 → recent commitsGET /api/v1/git/diff?path=<dir>&scope=all → unified diff (HEAD)GET /api/v1/git/diff?path=<dir>&scope=staged&file=<rel>GET /api/v1/git/show?path=<dir>&hash=<sha> → commit + patchGET /api/v1/git/remote?path=<dir> → owner/repo + token stateGET /api/v1/git/prs?path=<dir>&state=open → list pull requests```Most of the time the plain CLI is faster and the user expectsfamiliar git output. Reach for the gateway endpoints when:- you want to surface a structured PR list (no `gh`/`tea` setup needed)- the user wants you to *summarise* a long diff without dumping all of it into the chat — fetch the JSON, then paraphrase## Patterns### Quick status summary```bashgit -C "$PWD" status --shortgit -C "$PWD" log --oneline -5```### Review the working tree before committing```bashgit diff --stat HEADgit diff --cached # stagedgit diff # unstaged```### Show recent open PRs without per-CLI auth```bashcurl -s "http://127.0.0.1:8770/api/v1/git/prs?path=$PWD&state=open" \ | jq '.prs[] | {number, title, author, head, base}'```If `need_token: true` comes back, tell the user to add a token in theopendray Plugins page (Git hosts section) for the matching host.## ConventionsThis repo uses **conventional commits**:`<type>: <description>` where type ∈ {feat, fix, refactor, docs, test, chore, perf, ci}.Branch naming: `<type>/<short-slug>` (e.g. `feat/notes-vault`).PRs should:- have a 1-3 sentence summary at the top- include a Test Plan checklist- reference any related issue / decision note in `projects/<basename>/decisions/`## Safety- Never run destructive git ops without confirming the working tree state and asking the user- For force-push, rebase main, branch -D — always pause and confirm- Read-only endpoints are safe to call freely; PR listing hits remote APIs (GitHub/Gitea/GitLab), which counts against rate limits---> Source: [Opendray/opendray](https://github.com/Opendray/opendray) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions