git-workflow-and-versioning
An agent skill by addyosmani, from addyosmani/agent-skills. Tags: developer-tools, documents.
What it does
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add addyosmani/agent-skills --skill git-workflow-and-versioning
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/addyosmani/agent-skills
cp -r agent-skills/skills/git-workflow-and-versioning ~/.claude/skills/git-workflow-and-versioning
Safety box score
Grade C, moderate risk: 26 of 100 risk points, rated 2026-10-21. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is mostly local git workflow guidance: commits, branches, worktrees, and release tagging. It does not ship code or download anything, but it does instruct an agent to run project scripts, rewrite local history with `git reset --hard HEAD`, and push release tags to a remote.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 1 (low) | It tells the agent to run repository commands and scripts such as `npm test`, `npm run lint`, and `npx tsc --noEmit`; there are no bundled executables or code evaluators. |
| Network access | 1 (low) | The only explicit outbound action is release publishing via `git push origin v1.4.0`, which sends refs to a remote but does not fetch from arbitrary hosts. |
| Filesystem reach | 2 (moderate) | It can create and remove sibling worktree directories with `git worktree add ../project-feature-a ...` and `git worktree remove ...`, and it recommends hard resets that discard local file changes. |
| Secrets & credentials | 1 (low) | It scans staged diffs for `password|secret|api_key|token` and warns against committing `.env`, `.env.local`, and `*.pem`; it does not ask for credential-store access. |
| Privilege & persistence | 0 (none) | There is no sudo, service registration, global install, or shell/OS configuration in the skill. |
| Instruction hijack surface | 0 (none) | No hidden text or instruction to bypass policy appears; it only discusses git workflow practices and release hygiene. |
| Irreversible actions | 2 (moderate) | It directs publishing actions like `git push origin v1.4.0` and encourages `git reset --hard HEAD` to recover, which can delete or publish work without further internal checks. |
| Transparency | 0 (none) | The file is plain markdown with readable commands and no binaries, encoded blobs, or fetched code. |
Before installing
- Review the `git reset --hard HEAD` guidance and decide whether your workflow can tolerate local changes being discarded.
- Confirm that pushing release tags with `git push origin v1.4.0` matches your remote policy.
- Check whether creating sibling worktree folders like `../project-feature-a` is acceptable in your workspace.
- If you use this skill, run it first in a scratch repo so you can see the exact commit, tag, and worktree commands it will trigger.
Rated 2026-10-21 by an automated review of 1 file from the skill's repository.
Source
- Repository
- addyosmani/agent-skills (all skills from this repository)
- Path
- skills/git-workflow-and-versioning/SKILL.md
- Branch
- main
- Updated
- 2026-09-19
Related skills
- code-review-and-quality — Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human.
- constraint-driven-development — Establishes a project's quality bar as a written contract and stops agents quietly lowering it.
- context-engineering — Optimizes agent context setup.
- deprecation-and-migration — Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another.
- documentation-and-adrs — Records decisions and documentation.
- doubt-driven-development — Subjects every non-trivial decision to a fresh-context adversarial review before it stands.