shiplisted

You are automating the complete git workflow to ship code changes. After creating the PR, you will automatically review it, fix any issues, and merge it. The user may provide a branch name and description as arguments: $ARGUMENTS ## Proactive Triggers Suggest this skill when: 1. User says "done", "ready to ship", "push this", "let's ship it", or similar completion phrases 2. After completing a work item from an implementation plan 3. After all tests pass and changes are ready 4. User asks to create a PR or push changes 5. After a code review cycle is complete and changes are approved ## Destructive Action Warning This skill modifies git state (creates branches, commits, pushes, and merges). Before proceeding: - Confirm the user intends to ship the current changes - Never force-push or push to main/master directly - Always create a feature branch for changes - If the working directory has uncommitted changes that look unrelated, ask before staging everything ## Input Validation **Optional Arguments:** - `<branch-name>` - Custom branch name (default: auto-generated from changes) - `draft` - Create PR as draft - `--dry-run` - Preview all operations without making any changes - `--audit` - Log all git and PR operations to `.claude-plugin/audit.log` (see common-patterns.md) **Dry-Run Mode:** When `--dry-run` is specified: - Show what branch name would be created - Show what files would be staged and committed - Show the proposed commit message - Show the PR title and body t