$ man context-wiki/git-for-gtm

Think of Git like packing and shipping boxes. git add is putting items in the box. You pick which files go in this shipment. git commit is sealing the box and writing a label that describes what is inside. git push is shipping the sealed box to the warehouse (GitHub). Until you push, nobody else can see your work and your code is not backed up. It is just sitting on your local machine in sealed boxes. I did not understand Git until I needed to revert a broken homepage. I changed something, refreshed the page, and the entire layout was gone. Then I realized I could undo the commit and go back to when it worked. That is when it clicked. Git is not just tracking changes. It is letting you time travel.

PATTERN

Staging lets you control what goes into each commit. If you update your persona doc and that triggers changes to campaign angles and pain points, you want all of those in the same box. That way you can roll back the whole thing if your hypothesis was wrong. Bad practice: committing everything at once with a message like "updates". You cannot isolate what changed or why. Good practice: staging related changes together with a descriptive message. "Update acme persona tiers and adjust campaign angles for tier 2" tells you exactly what happened and why. When something breaks, you know which box to open.

CODE

git add . (stage all changed files for the next commit) git commit -m "your message here" (seal the box with a label) git push origin main (ship to GitHub) That is it. Three commands cover 90% of daily Git usage. The /deploy skill runs all three automatically, plus build verification and deploy confirmation. You do not need to memorize Git. You need to understand the concept and let the skill handle the execution.

PRO TIP

Every commit is a save point. If you break something, you can go back. git log shows your history. git revert undoes a specific commit without erasing history. git checkout lets you look at old versions of files. This is why commit messages matter. When you are scrolling through git log trying to find where things broke, "fix stuff" tells you nothing. "Add hero section animation" tells you exactly which commit introduced the change. Good messages are not for Git. They are for future you at 11 PM trying to figure out what went wrong.