# Push > Push to GitHub Skill - Skill: `valasubramanian-kr/push` (Agent Skill) - Install (CLI): `npx skillmds@latest add valasubramanian-kr/push` - Raw SKILL.md: https://api.skillmd.com/api/skills/valasubramanian-kr/push/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: valasubramanian-kr (https://skillmd.com/u/valasubramanian-kr) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/valasubramanian-kr/push --- # Push to GitHub Skill ## Purpose Commit changes, push to GitHub, and create a pull request linked to the JIRA issue. ## Usage ```bash /push ``` (Must be run after `/validate` with all tests passing) ## What This Skill Does 1. **Verify Tests Pass**: Confirms validation-results.md shows passing tests 2. **Verify Branch**: Ensures on correct `dcppay-*` branch 3. **Stage Changes**: Adds all modified files to git 4. **Create Commit**: Generates conventional commit message 5. **Push to GitHub**: Pushes branch using GitHub MCP 6. **Create Pull Request**: Auto-populates PR with JIRA link and details 7. **Save PR Details**: Outputs PR URL to `pr-details.md` ## Validation Results Context The validation results should be located in the most recent directory under `workflow/jira-to-github/*/validation-results.md`. You will need to find and read this file in Step 2. ## Current Issue Context The JIRA issue details should be located in the most recent directory under `workflow/jira-to-github/*/current-issue.md`. You will need to find and read this file in Step 1. ## Development Branch Context The development branch details should be located in the most recent directory under `workflow/jira-to-github/*/dev-branch.md`. You will need to find and read this file in Step 1. ## Instructions You are pushing changes to GitHub and creating a pull request. Follow these steps: **CRITICAL**: Your ONLY job is to: 1. Verify code and validation results 2. Stage and commit changes 3. Push the changes to only development branch in specific project repo 4. Create a PR following the standards **DO NOT**: - Push code to other branches - Delete any branches - Delete any PR ### Step 1: Validate Prerequisites Verify that: 1. Currently on the correct `dcppay-*` branch 2. Changes have been made to the codebase 3. Validation has been run ```bash # Check current branch CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD) # Verify branch matches expected pattern if [[ ! $CURRENT_BRANCH =~ ^dcppay-[0-9]+-.*$ ]]; then echo "❌ Not on a dcppay development branch" exit 1 fi # Check for changes if [ -z "$(git status --porcelain)" ]; then echo "❌ No changes to commit" exit 1 fi # Verify validation results exist JIRA_DIR=$(ls -td workflow/jira-to-github/*/ 2>/dev/null | head -1) if [ ! -f "$JIRA_DIR/validation-results.md" ]; then echo "❌ No validation results found. Run /validate first." exit 1 fi ``` ### Step 2: Verify Validation Passed Verify that: 1. Validation results exist and all tests passed Read validation-results.md and verify: - All tests passed ✓ - No critical issues - Linting passed - Type checking passed **If validation failed, STOP**: ``` ❌ Cannot create PR - validation failed Fix failing tests first, then run /validate again. ``` ### Step 3: Review Changes Show what will be committed: ```bash # Show changed files git status # Show diff summary git diff --stat ``` ### Step 4: Stage Changes Ask the user what they want to commit and push: **Use AskUserQuestion tool**: ``` Question: "What would you like to commit and push?" Options: 1. "All modified files (staged + unstaged)" - Stage all changes with git add . 2. "Only staged files" - Use files already staged by user 3. "Skip staging (already committed)" - Skip to push step ``` **Then based on the answer**: **Option 1: All modified files** ```bash # Stage all changes git add . # Verify staged files git status ``` **Option 2: Only staged files** ```bash # Show what's already staged git diff --cached --stat # Verify staged files exist if [ -z "$(git diff --cached --name-only)" ]; then echo "❌ No files are staged. Stage files first with: git add " exit 1 fi ``` **Option 3: Skip staging (already committed)** ```bash # Verify there are commits to push if [ -z "$(git log origin/$CURRENT_BRANCH..$CURRENT_BRANCH 2>/dev/null)" ]; then echo "❌ No commits to push" exit 1 fi # Show commits that will be pushed git log origin/$CURRENT_BRANCH..$CURRENT_BRANCH --oneline # Skip to Step 7 (Push to GitHub) ``` **Exclude from staging**: - `.env` files - `node_modules/` - Build artifacts (`dist/`, `build/`) - Personal IDE configs (`.vscode/`, `.idea/`) - Test coverage reports ### Step 5: Generate Commit Message Create a conventional commit message: **Format**: ``` : Refs: ``` **Types**: - `feat`: New feature - `fix`: Bug fix - `refactor`: Code refactoring - `test`: Adding tests - `docs`: Documentation - `style`: Code style changes - `perf`: Performance improvements - `chore`: Maintenance tasks **Example messages**: ``` feat: add eProtect error code handling - Implement error code mapping for eProtect responses - Add user-friendly error messages - Update analytics events for error tracking Refs: DRT-17270 ``` ``` fix: resolve card deletion bug - Fix issue where cards weren't removed from Zustand store - Sync card state across wallet, flyout, and checkout - Add unit tests for card deletion Refs: DRT-17345 ``` ``` feat: implement checkout intent orchestration - Add new controller endpoint for checkout intent - Implement module business logic - Add domain models for checkout - Integrate with upstream payment service Refs: DRT-17410 ``` ### Step 6: Create Commit Commit the staged changes: ```bash # Create commit with message git commit -m "" # Verify commit created git log -1 --oneline ``` ### Step 7: Push to GitHub Push the branch to GitHub: **Option A: Using GitHub MCP** ``` Use mcp__github__createCommit or mcp__github__push tools ``` **Option B: Using git command** ```bash # Push to origin git push -u origin $CURRENT_BRANCH # Verify push successful git log origin/$CURRENT_BRANCH -1 --oneline ``` ### Step 8: Load PR Template from Repo Profile Load the repo-specific PR template: 1. Read `workflow/jira-to-github/*/target-repo.md` to get the profile path 2. Read the repo profile (e.g., `context/repos/esperanto.md`) 3. Extract the `PR Template` section — use it for the PR title format and body structure 4. If `target-repo.md` or the profile is not found, fall back to the default template below **Handle Labels from profile:** Read the `### Labels` subsection within the PR Template: - If it contains `(select)` marker (e.g., `### Labels (select)`): - Parse the label options (each line: `-