[Claude Code Introduction E38] Automation of commit creation: Procedure·Smart Message·Conventional Commits·HEREDOC·Co-Authored-By

Original author：새로운 시작 (neosarchizo)

Original source：https://www.youtube.com/embed/srE5CtDbDQI

Many of the channel's translated audio tracks are produced with HeyGen. If you are interested in AI video translation, dubbing, and multilingual content creation, try HeyGen here: https://bit.ly/4o4bn9P You can help the channel by subscribing through this link — thank you! This is the second lesson in Section 8 (Git Integration Workflow). If lesson 37 was the foundation for reading changes (status·diff·log) and safely handling them, lesson 38 was the first work on top of that – creating commits. First, let's clear up a misunderstanding: there is no built-in /commit slash command. Commit is called in natural language, and Claude executes it as a procedure using Bash tool. It covers the process, smart messages, Conventional Commits, HEREDOC, and even the Co-Authored-By trailer. 📌 What we cover - There are no /commit slash commands — you can just say something in natural language like "commit changes" and Claude will run the commit process in Bash. The last step of best practice, Explore → Plan → Implement → Commit, is also natural language, such as “Commit with an explanatory message and open PR” - Commit is a procedure, not a command — git status (what) → git diff (how) → git log (old style) → message → git add → git commit → git status (confirm). The first three are read-only git, so they run automatically and in parallel, and half of their “smartness” lies in conforming to repository conventions with git log. And a good message is not the “what” but the “why” — what the diff already shows — Conventional Commits format — Type[Scope]: Description + Body + Footer. feat → MINOR · fix → PATCH · BREAKING CHANGE (! or footer) → MAJOR, in conjunction with SemVer, the changelog · release automation parses. However, Claude follows the conventions of your repository, so if you want to force it, write it in CLAUDE.md (Lesson 21) - Multilines with text are HEREDOC — The 'EOF' delimiter wrapped in single quotes prevents the shell from interpreting $·backticks and preserves the message literally. An idiom that solves multi-lines, special characters, and correct formatting all at once - Co-Authored-By: Claude Display honestly with a trailer — GitHub recognizes you as a co-author (the active model name can be entered), leaving the git config untouched. Author as person and contribution as trailer. To turn it off or change it, empty or change commit·pr with the attribution setting (formerly includeCoAuthoredBy, default true) - 37th Safety principles remain the same in commits — commit only when requested, branch first if it is the default branch, prohibit hook skipping (--no-verify), commit newer than --amend, exclude sensitive files. Nail it with allow Bash(git commit *) + deny Bash(git push *) 📌 Environment information - Latest version of Claude Code - Commit call: natural language ("commit changes") · No built-in /commit · Git built-in is /diff·/code-review·/security-review·/install-github-app - Commit procedure: git status → git diff (+ --staged) → git log → write message → git add (related file only) → git commit → git status - Multi-line: HEREDOC idiom · The 'EOF' delimiter wrapped in single quotes prevents the shell from interpreting $·backticks, preserving the message literally - Conventional Commits: Type [Scope]: Description + Body + Footer · feat → MINOR · fix → PATCH · BREAKING CHANGE (! or footer) → MAJOR - Contribution Mark: Commit = Co-Authored-By: Claude (noreply@anthropic.com) Trailer · PR = 🤖 Generated with Claude Code Footer (39th session) - Attribution settings (introduced in v2.0.62, previously includeCoAuthoredBy default true): Turn off commit·pr to "" or change the wording - Permission rules: allow Bash(git commit *) · deny Bash(git push *) · headless --allowedTools "Edit,Bash(git commit *)" - Safe: Request to specify commit·push · Protect default branch · Prohibit --no-verify · --amend Careful (authorship check) · Exclude .env·*.key 📌 Chapter 0:00 Introduction — Commit becomes more important in the agent era 0:41 There is no such thing as /commit — Commit is called natural language 1:29 Commit is not a command, but a procedure — status→diff→log→message→add→commit→status 2:37 Good commit message — “why” not “what” 4:06 Conventional Commits format — type[scope]: description and SemVer 6:31 body and HEREDOC — multiline safe 7:26 Co-Authored-By — don’t touch git config, just contribute honestly 8:18 turn off or change attribution setting (formerly includeCoAuthoredBy) 9:09 37th session Safety principle — commit first Branch·allow commit·deny push 10:20 Cleaning up common pitfalls 📌 Reference links - Blog: https://neosarchizo.github.io/posts/claude-code-38-commit-generation - Best practices — Explore→Plan→Implement→Commit workflow, “Commit with descriptive message and open PR”, CLAUDE.md repository etiquette: https://code.claude.com/docs/en/best-practices - General workflow — Change summary·PR creation prompt recipe, gh pr create session link: https://code.claude.com/docs/en/common-workflows - Settings — attribution (customize commit·PR contribution display) and deprecated includeCoAuthoredBy (default true): https://code.claude.com/docs/en/settings - Conventional Commits v1.0.0 — Type[scope]: Description structure, feat/fix and SemVer, BREAKING CHANGE: https://www.conventionalcommits.org/en/v1.0.0/ - Command reference — List of built-in commands (/diff·/code-review, etc., no /commit): https://code.claude.com/docs/en/commands #ClaudeCode #Git #CommitAutomation