Gett Push — Git Workflow for gtforge Repos

Quick Check

Run git remote -v. If the remote does not contain gtforge, stop here — this skill does not apply. Fall back to normal git behavior.

The Pipeline

Every commit/push/PR request follows this pipeline. Execute all applicable steps — if the user says "commit", that means commit + push + PR. The goal is to get changes reviewed with minimal friction.

Step 1: Jira Ticket

Look for a Jira ticket in the conversation. The user may provide:

• A full URL: https://gett.atlassian.net/browse/GETT-12345
• Just the ID: GETT-12345

If no ticket was mentioned, ask the user for one. They can say "none" — that's fine, proceed without it.

Fetching the story name: If the Atlassian MCP tools are available (getJiraIssue), use them to fetch the ticket summary. If the MCP is not available, infer a concise story name from the diff and the conversation context, then confirm with the user (e.g., "I'd call this 'No validation error on screenshotDisabled text fields' — sound right?").