checkpointlisted

# /checkpoint — Save Point Quick finalization workflow. Ships work with a version bump in one command. Use when the full `/finish` protocol (rebase, squash, verify) isn't needed — the work is already clean and tested. ## Invocation ``` /checkpoint # Auto-detect bump type + commit + push /checkpoint patch # Bump patch + commit + push /checkpoint minor # Bump minor + commit + push /checkpoint major # Bump major + commit + push /checkpoint patch "feat: add scoring" # Explicit commit message for work changes ``` ## Workflow ### 1. Commit Work If uncommitted changes exist (staged or unstaged): - Stage changes: `git add` relevant files (not `-A` — be deliberate) - Commit with provided message, or derive from branch name and changes - Use conventional commit format: `<type>(<scope>): <subject>` If working tree is clean, skip to step 3. ### 2. Detect Bump Type (if not specified) If no bump type was passed, scan git log since the last version tag: ```bash git log $(git describe --tags --abbrev=0 2>/dev/null)..HEAD --oneline 2>/dev/null || git log --oneline ``` Apply the highest-precedence rule found: | Commit prefix | Bump type | |---------------|-----------| | `BREAKING CHANGE` in body, or `!` after type (e.g. `feat!:`) | major | | `feat:` | minor | | `fix:`, `perf:`, `refactor:`, etc. | patch | - If multiple rules match, use the highest precedence (major > minor > patch). - If no convent