Skip to content
SkillModel-led3,212 tokens in use

git-workflow-and-versioning

Keep git history reviewable with trunk-based branches, atomic commits, clear messages, worktrees and SemVer releases.

119,377 stars on the repository MIT Licenseaddyosmani/agent-skills · skills/git-workflow-and-versioning
npx skills add addyosmani/agent-skills --skill git-workflow-and-versioning
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing git-workflow-and-versioning costs

132tokens idle
3,212tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetectedgitdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure17/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs git commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 102
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 153

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community76
  • Maturity32
  • Momentum40

Git Workflow and Versioning sets the git habits an agent follows on every code change. Commits are save points, branches are short-lived sandboxes and history serves as documentation.

The skill covers atomic commits, commit message format, change sizing, git worktrees for parallel agents, structured change summaries, pre-commit checks, git bisect and blame, and a release section on semantic versioning, tags and human-written changelogs.

What You Get

  • Rules for atomic commits, messages and change sizing
  • A branching and worktree workflow for parallel work
  • A pre-commit hygiene routine with a secrets check and git bisect, log and blame commands
  • Semantic versioning, tagging and changelog guidance with verification lists

Common Use Cases

  • Writing a commit message
  • Splitting a large change into commits
  • Running several agents in parallel branches
  • Choosing a version bump and writing a changelog

What Makes It Unique

The skill pairs commit discipline with a release section that treats the tag as the single source of the version and treats the changelog as a document written for consumers. It also asks for a change summary that names what the agent chose not to touch.

Under The Hood

The SKILL.md loads on any code change. The commands it describes run git for commits, branches, worktrees, bisect, blame, tags and pushes, and the project’s test, lint and type check commands. Pushing a tag reaches the remote. It ships no scripts.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers