What problem does it solve? Code-based video projects (such as Remotion compositions) need version control that survives closed laptops, explains why values were chosen, and lets multiple people work on one project without emailing folders around. This Skill defines what to track, how to commit, how to undo, and how to publish a cleaned repository. ## Core Features & Use Cases - Tracking Rules: Track source, content, scripts, and assets; exclude node_modules, renders, and .env files, with the reasoning behind each rule. - Commit and Undo Discipline: Commit when something works, write why-focused messages, branch for uncertain work, and use revert or restore to walk history back. - Multi-Person Collaboration: Separate prose (which conflicts badly) from code (which conflicts mechanically), avoid sequentially numbered files, and reconcile shared documents deliberately. - Clean Publishing: Build a new repository from current contents instead of forking, so abandoned large assets in history are not shipped. - Use Case: Two contributors and an AI assistant share one Remotion video repository; this Skill keeps their work recoverable, conflict-minimal, and publishable without its full history. ## Quick Start Ask your coding assistant to set up Git for this video project following the collaborating-with-git skill, including what to track and how to handle commits.
