git-conventions
/git-conventions
Pilnuje konwencji commitów: typów conventional commits, formatu wiadomości 50/72, rytmu TDD i standardów pull requestów.
- Autor
- itzcull ↗
- Repozytorium
- software-skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 04.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 04.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pilnuje konwencji commitów: typów conventional commits, formatu wiadomości 50/72, rytmu TDD i standardów pull requestów.
Oryginalny opis (EN)
Git commit conventions covering stability invariants, conventional commit types (feat, fix, refactor, test, chore), message formatting (imperative voice, 50/72 rule), TDD commit rhythm (stable checkpoints after GREEN and REFACTOR), and PR standards. Use when writing commit messages, structuring commits, or reviewing git history quality.
Jak działa
- Purpose
- Relationship to structured development
- When to use
- Key principles
- Reference files
Podgląd SKILL.md
--- name: git-conventions description: Git commit conventions covering stability invariants, conventional commit types (feat, fix, refactor, test, chore), message formatting (imperative voice, 50/72 rule), TDD commit rhythm (stable checkpoints after GREEN and REFACTOR), and PR standards. Use when writing commit messages, structuring commits, or reviewing git history quality. license: MIT metadata: author: itzcull --- ## Purpose Define the conventions for git commits that maintain a clean, bisectable, and meaningful project history. Every commit represents stable, working software with incremental, focused changes. ## Relationship to structured development Within [structured development](../structured-development/SKILL.md), this skill supplies [traceable change records](../structured-development/SKILL.md#conformance-requirements) and information for [review or continuation at scope handoff](../structured-development/SKILL.md#7-close-the-agreed-scope) across increments. Its commit boundaries preserve understandable history; they are not substitutes for the enclosing procedure's acceptance or release boundaries. Use the intended change, repository policy, available verification evidence, and the Git operation the user has authorized. Return proposed commit boundaries and messages, or the resulting commit or PR references when execution is requested, with an honest account of verification. Apply TDD-specific cadence when the procedure uses TDD rather than imposing test-first development on every procedure. A commit records a change; a PR presents it for review. Neither establishes acceptance or release readiness. If stability cannot be demonstrated, report the missing or failed checks instead of asserting a verified commit. This skill's conventions do not independently authorize committing, pushing, or merging. ## When to use - Writing commit messages - Deciding what to include in a single commit - Structuring commits during TDD (when to commit in RED-GREEN-REFACTOR) - Reviewing commit history quality - Setting up commit conventions for a new project - Understanding conventional commit types and their usage ## Key principles - **Stability first** - every commit must satisfy the repository's applicable stability checks; skipped required checks are not passes - **Incremental progress** - small, focused changes easy to review, revert, and bisect - **Imperative voice** - describe what the code DOES when applied - **Semantic clarity** - type prefixes indicate the nature of change at a glance - **TDD rhythm** - use stable checkpoints after GREEN and REFACTOR within the enclosing procedure's authorized commit boundaries ## Reference files - [Git commit conventions](references/git-commits.md) - Complete guide including stability invariants, commit types, message formatting, TDD commit rhythm, and PR standards
Pliki w paczce (2)
- SKILL.md 3 KB
- references/git-commits.md 9 KB
Wersje
W bazie nie ma innych skilli o nazwie git-conventions.
Migawka bazy z 13.11.2026 · wersja paczki 60213d8ce952 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100conventional-commit
Pisze i waliduje komunikaty commitów zgodne ze specyfikacją Conventional Commits 1.0.0, także gdy użytkownik prosi tylko o zrobienie commita. - 100commit-message
Generuje komunikaty commitów w formacie conventional commits i pomaga przy tworzeniu commitów git. - 100plei-git
Pisze i przegląda komunikaty commitów zgodne z Conventional Commits oraz opisy pull requestów. - 95git-commits
Pisze jasne komunikaty commitów i tytuły pull requestów według Conventional Commits, poprawiając historię zmian. - 90Conventional Commits
Podaje wzorce Conventional Commits, czyli spójne i czytelne maszynowo komunikaty commitów. - 100commit
Tworzy komunikaty commitów według konwencji Sentry: conventional commits z odwołaniami do zgłoszeń Sentry.