deploy-shiplisted

# Deploy and Ship **Announce:** "I'm using enggenie:deploy-ship to [commit/create PR/complete branch]." ## The Last Mile Code is verified. Tests pass. Now ship it cleanly. This skill handles commits, PRs, Jira updates, and branch completion - the final steps before the next story begins. --- ## 1. Commit ### Analyze Staged Changes Run `git diff --staged` and read the full output. Understand what changed and why before proposing a message. ### Propose a Conventional Commit Message Format: ``` <type>: <description> [optional body - explain WHY, not what] ``` **Types:** | Type | When | |------|------| | feat | New capability for the user | | fix | Bug fix | | refactor | Code restructure, no behavior change | | docs | Documentation only | | test | Adding or updating tests only | | perf | Performance improvement | | style | Formatting, whitespace, linting (no logic change) | | chore | Build, config, tooling, dependencies | **Rules:** - Present tense: "add search endpoint", not "added search endpoint" - Subject line under 72 characters - Body explains WHY, not just what changed - One logical change per commit - if the diff spans unrelated concerns, suggest splitting ### Wait for Confirmation Present the proposed message to the user. NEVER auto-commit. The user confirms, edits, or rejects. ``` Proposed commit: feat: add pagination to search results Unbounded result sets cause timeouts on datasets over 10k rows. Default page size of 50 with cursor-based navigati