klausborges/workflow-skills111 installs

git-conventions

Q: How do I install this agent skill?

Run npx skills add https://github.com/klausborges/workflow-skills --skill git-conventions.

Q: Is this agent skill safe to install?

Review the displayed partner audits, complete source, permissions, dependencies, and exact revision before installing.

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.

How do I install this agent skill?

npx skills add https://github.com/klausborges/workflow-skills --skill git-conventions

view source ↗

Is this agent skill safe to install?

Gen Agent Trust Hubpass
This skill consists of documentation and style guidelines for Git workflows. It does not contain any code, external dependencies, or instructions that could lead to security vulnerabilities.
Socketpass
No alerts
Snykpass
Risk: LOW · No issues

What does this agent skill do?

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.

How can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/klausborges/workflow-skills/git-conventions">View git-conventions on skillZs</a>