Long-form docs
Fixed sections—context, proposal, risks, migration—for async review and cross-team decisions; ideal for architecture changes.
Category · Git & delivery workflow
Git & delivery workflow
5 skills Category 17 of 20
This category turns collaboration norms into habits: RFC-style long-form docs, branching/merge policies, Conventional Commits, generated changelogs, and PR templates. It complements docs & knowledge—process and engineering workflow vs. wiki information architecture.
In the hub it opens the “process & docs” band. The five entries match the main hub.
Quick links
In depth
Git workflow
Trunk-based, GitFlow, or simplified variants—align with release cadence, feature flags, and code owners.
Conventional Commits
feat/fix/docs types with scopes to drive release notes and semantic versioning hints.
Changelog generation
Aggregate user-visible changes from commits or PR labels; separate BREAKING with migration notes—ship with releases.
PR description
Motivation, approach, test evidence, rollback, risks—helps reviewers judge merge impact quickly.