SkillsAdd

klausborges/workflow-skills

git-conventions

Shared git conventions for personal repos covering remote naming, primary remote choice, conventional commit shape, worktree placement, and commit/PR writing style.

First seen Jul 22, 2026

Installation

$ npx skills add klausborges/workflow-skills --skill git-conventions
View on skills.sh ↗ GitHub repository ↗

Summary

  • Shared git conventions for personal repos covering remote naming, primary remote choice, conventional commit shape, worktree placement, and commit/PR writing style.
  • Use when setting up or renaming remotes, choosing where to push or open PRs, deciding where a worktree lives, or when another git skill points here.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

find-skills Same topic
vercel-labs/skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "fi…

3.3M installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-prepare Same topic
microsoft/azure-skills

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Te…

568.3K installs

Also in this package

Other skills from klausborges/workflow-skills · top by installs.

npx skills add klausborges/workflow-skills
explain-codebase 120 improve-architecture 113 plan-work 113 plan-prototype 112 diagnose-issue 111 write-handoff 111 explain-workflow 111 review-work 111 use-workflow 111 implement-work 111

Browse all from klausborges/workflow-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,525 B
  • docs SUMMARY.md 336 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 110 installs

SKILL.md

Git Conventions

Remotes

  • Name remotes by host: github for GitHub, forge for the personal Forgejo instance. Never origin.
  • Set up both remotes when possible; the second acts as a backup mirror.
  • Each repo picks one primary remote at setup. The primary owns CI and pull requests, and is what "origin" means in conversation. Default primary: github.

Commits and PR titles

First line is type(scope): description, scope optional. Types: feat, fix, docs, ci, build, chore, refactor, test, perf, revert.

Worktrees

Worktrees are optional. Manual ones live at <repo>/.worktrees/<branch> with slashes flattened to dashes, and the directory stays gitignored. Native harness worktree homes (for example Claude Code's .claude/worktrees/) are equally fine. Keep project folders free of bare worktree siblings.

Writing style

  • Plain sentences with periods and commas; sentence-case headings.
  • Write for the repo's durable history: describe the change itself, never plans, milestones, or phases. Branch names may keep stack prefixes like m2/prng since branches are deleted at merge.
  • Skip emdashes and decorative emoji.