What problem does it solve? Unfinished work sitting uncommitted in a local session is one crash or context loss away from disappearing. This Skill backs up in-progress work to a remote GitHub branch as a safety net, without merging, deploying, or ever touching the main branch that publishes the live site. ## Core Features & Use Cases - Safe branch handling: If invoked on main, it first moves the work to a new wip/<topic> branch, since pushing main would publish the site. - Scoped staging: Classifies every changed file as in-scope or out-of-scope and stages only explicit file paths, never using git add -A. - Non-blocking lint check: Runs npm lint (plus the website workspace lint when relevant) and flags failures in the report without blocking the backup. - Conventional commits: Commits in the repo's feat/fix/chore style so checkpoint commits remain valid history when later merged. - Use Case: Midway through refactoring a navigation component, you say "save my progress" — the work is committed, pushed to a remote branch, and the session continues on that branch until you say ship or park. ## Quick Start Ask the assistant to checkpoint the current session's work so it is committed and pushed to a remote branch while you keep working.
