# Github > GitHub workflow conventions: writing clear conventional commits, opening detailed issues and PRs via the `gh` CLI, and choosing trunk-based vs short-lived branch flow based on the size of the change. Use whenever the user wants to commit, branch, push, open an issue, open a PR, or asks how to structure any of those. Keep it light — direct, detailed messages, no ceremony. - Skill: `nodatime/github` (Agent Skill) - Install (CLI): `npx skillmds@latest add nodatime/github` - Raw SKILL.md: https://api.skillmd.com/api/skills/nodatime/github/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: nodatime (https://skillmd.com/u/nodatime) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/nodatime/github --- # GitHub workflow The point: write commits, issues, and PRs that read clearly weeks later. Be direct, be specific, skip the filler. ## Branching — when to branch, when not Always create a branch, with a short slug. When fixing an issue, the branch name should be `issue-`. Otherwise, a few words, hyphen-separated, is fine. ## Commits Noda Time does not use conventional commits. Format: ```