park

Commits session work to a remote branch and returns to a clean main.

1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/robritacca-dotcom/design-system --skill park-robritacca-dotcom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: park
Source: https://github.com/robritacca-dotcom/design-system/tree/main/.claude/skills/park
Command: npx skills add https://github.com/robritacca-dotcom/design-system --skill park-robritacca-dotcom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an experiment or work-in-progress needs to be set aside, developers risk losing uncommitted changes or polluting the main branch. This Skill shelves the session's work safely: it commits everything to a named remote branch, then returns the working tree to a clean main so something else can start immediately. ## Core Features & Use Cases - Branch-safe shelving: Creates a wip/<topic> branch if on main, commits in the repo's conventional style, and pushes to the remote without merging or deploying anything. - Scoped staging discipline: Surveys git status and stages only explicit in-scope file paths, never blanket git add -A, and never commits credentials or .env files. - Resume-ready reporting: Reports the branch name, each commit hash and subject, lint status, and any files left out, so the work is easy to pick up later. - Use Case: You spent a session prototyping a new component but priorities shifted. Ask to park it, and the work lands on wip/new-component on the remote while your local tree returns to a clean main. ## Quick Start Ask the assistant to park this session's work so it is committed and pushed to a named branch while the repository returns to a clean main.

Frequently Asked Questions about park

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I shelve uncommitted git work without losing it?

Commit the work to a named branch such as wip/<topic>, push it to the remote with git push -u origin <branch>, then check out main. The branch remains on the remote as the only copy, so nothing is lost and nothing merges or deploys.

What is the difference between parking, checkpointing, and shipping a branch?

Parking pushes the branch and returns to a clean main, ending the session off the work. Checkpointing pushes the branch but keeps working on it. Shipping merges into main, pushes, and deploys. Parking is the right choice when setting an experiment aside.

Does parking a branch deploy or merge anything?

No. Parking only commits to a work branch and pushes that branch to the remote. It never commits to main, never merges into main, and never triggers a deployment. The session ends back on a clean main branch.

Why should I avoid git add -A when committing session work?

Blanket staging can sweep in out-of-scope files, credentials, or .env files that should never be committed. Staging explicit file paths keeps the commit limited to the session's actual work and prevents accidental secret leakage.

What happens if lint fails when shelving work in progress?

A lint failure does not block the park, since a shelved experiment is allowed to be mid-mess. The failure is recorded in the report so whoever resumes the branch knows the state of the work before continuing.