---
title: Conventional Commits, SemVer and Repo Templates | Relic
description: The conventions that make a repo pleasant to work in: conventional commits, semantic versioning, and pull request and README templates you can copy today.
canonical: https://relic.space/blog/topics/shipping-code
source: https://relic.space/llms.txt
---
Topic

# Shipping better code

Good repos run on a few small conventions: commit messages a tool can parse, version numbers that mean something, and templates that make the next contribution easier than the last. This series covers each one, with copyable examples.

Start here

[Pillar·9 minConventional Commits, explained accuratelyA small, strict format for commit messages that both people and tools can read. The spec accurately, why feat means MINOR and fix means PATCH, and how to adopt it without the process turning sour.Read ](https://relic.space/blog/conventional-commits)

In this topic

[7 minSemantic versioning (SemVer), explainedThe MAJOR.MINOR.PATCH scheme behind almost every package you install. What bumps what, the odd 0.x rules, version ranges in npm and pip, and the one promise SemVer quietly cannot keep.Read ](https://relic.space/blog/semantic-versioning)[7 minA pull request template you can copy todayA Markdown file your host pre-fills into every new PR. Three templates to copy, where the file lives on GitHub and GitLab, and what separates a checklist people use from one they delete.Read ](https://relic.space/blog/pull-request-template)[6 minA README template that people actually readThe front door of a project, and most visitors decide within the first screen. A copyable README skeleton that leads with the quick start, plus the reasoning and a minimal variant.Read ](https://relic.space/blog/readme-template)
