agis/git-style-guide resource
A Git Style Guide observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4175
- days_rel: n/a
- days_push: 1437
- n_releases_24m: 0
Adoption not part of the score
5115 stars · 410 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A community-driven Git style guide covering branch naming, commit messages, merging, and general Git workflow conventions. It is a documentation resource inspired by Linux kernel contribution practices and git man pages, available in many translations.
Use cases
- standardize git branch naming across a team
- write better commit messages
- define a team git workflow convention
- learn git best practices for merging
- onboard new developers to a git style guide
When to choose
- you want a well-established, widely-translated reference for git conventions
- you need a starting point for your team's git style guide
- you want guidance on branch naming and commit message style
When to avoid
- you need tooling that enforces conventions automatically
- your team already follows a different standard like Conventional Commits
- you need a tutorial for learning git from scratch
Facets
learning-resource · maturity maintenance
documentation version-control developer-tools version-control developer-tools documentation cross-platform git style-guide best-practices conventions branching commit-messages
1 source
- readme: https://github.com/agis/git-style-guide · fetched 2026-08-28 · d3bb9552d7e0
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| agis/git-style-guide | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="agis/git-style-guide")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem