How do I install the Git Workflow skill?

Run npx skillmds@latest add tomevault-io/git-workflow 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

File contents

Git and GitHub workflow

Tools: always git for repo and history, gh for PRs, issues, Actions, and repo hosting.

Repo rules

Branching: always commit to current branch; only if I ask, topic branch. Commands: prefer git switch and git restore; never run git pull blindly; always git push --force-with-lease; never git push --force. Sync: always git fetch; then ask the user before running git rebase <remote>/<branch> or git merge <remote>/<branch>. Push: if rewrite needed, use --force-with-lease, never plain --force. Recovery: use git reflog before panic.

Commit rules

Before: always git status; then git diff, then git diff --cached, then git --no-pager log --pretty=format:'%h %s (%cr) <%an>' -n 50. Then: always small, atomic commits; prefer split unrelated changes. Subject: short, imperative, informative; prefer <= 50 chars. Body: blank line, then why/constraints when non-obvious. Wrap: commit body prose at ~72 chars. Types: feat|fix|refactor|build|ci|chore|docs|style|perf|test. Scope: prefer no scopes; if codebase gets bigger, prefer based on repo's modules, historical/long-term support; never vague; always ask user before new scope. Footers: use BREAKING CHANGE: and trailer-style footers when needed.

GitHub rules

Tracking files

Gitignore: always toptal-like, with comments.

Source: alnah/agent — distributed by TomeVault.

---name: git-workflowdescription: Git and GitHub workflow. Use for status, diffs, commits, syncing with remote, recovery, PRs, issues, and GitHub Actions. Use when this capability is needed.---# Git and GitHub workflowTools: always `git` for repo and history, `gh` for PRs, issues, Actions, and repo hosting.## Repo rulesBranching: always commit to current branch; only if I ask, topic branch.Commands: prefer `git switch` and `git restore`; never run `git pull` blindly; always `git push --force-with-lease`; never `git push --force`.Sync: always `git fetch`; then ask the user before running `git rebase <remote>/<branch>` or `git merge <remote>/<branch>`.Push: if rewrite needed, use `--force-with-lease`, never plain `--force`.Recovery: use `git reflog` before panic.## Commit rulesBefore: always `git status`; then `git diff`, then `git diff --cached`, then `git --no-pager log --pretty=format:'%h %s (%cr) <%an>' -n 50`.Then: always small, atomic commits; prefer split unrelated changes.Subject: short, imperative, informative; prefer <= 50 chars.Body: blank line, then why/constraints when non-obvious.Wrap: commit body prose at ~72 chars.Types: `feat|fix|refactor|build|ci|chore|docs|style|perf|test`.Scope: prefer no scopes; if codebase gets bigger, prefer based on repo's modules, historical/long-term support; never vague; always ask user before new scope.Footers: use `BREAKING CHANGE:` and trailer-style footers when needed.## GitHub rulesPRs: open or merge if the user asks, or the repo clearly uses PR review.Auth: `gh auth status` when auth or host context unclear.Repo: `gh repo view|create|fork|clone`.Issues: `gh issue list|view|create`.CI: `gh run list|view|watch`.Merge: use `gh pr merge` with explicit strategy.## Tracking filesGitignore: always toptal-like, with comments.---> Source: [alnah/agent](https://github.com/alnah/agent) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Git Workflow