一键导入
git-push-remote
Push the current branch to the remote repository with upstream tracking
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Push the current branch to the remote repository with upstream tracking
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Find a git branch by Linear ticket ID prefix (e.g., STU-15)
Create or reuse a dedicated git worktree for a branch using a deterministic path layout
Create and maintain implementation progress documentation for a feature branch
Find the worktree path for a branch and create/reuse it when missing
Resolve a properly named git branch from a Linear ticket ID following the convention {type}/{ticket-id}-short-description
Fetch unresolved review threads and PR comments for the pull request tied to the resolved target branch
基于 SOC 职业分类
| name | git-push-remote |
| description | Push the current branch to the remote repository with upstream tracking |
Push the current branch to the remote repository, setting up tracking if needed.
In worktree workflows, run this skill from the ticket's dedicated worktree path.
worktree_path (recommended): absolute path to the ticket worktreebranch (optional): branch name; if omitted, resolve from the worktreeResolve working context:
If worktree_path is provided, prefer explicit -C commands:
git -C "{worktree_path}" rev-parse --show-toplevel
git -C "{worktree_path}" branch --show-current
If branch is not provided, resolve it from the same path.
If branch resolves to empty (detached HEAD), stop and return an actionable error.
Confirm repository/worktree location:
Check if upstream is set:
git -C "{worktree_path}" rev-parse --abbrev-ref --symbolic-full-name "@{upstream}" 2>/dev/null
Push to remote:
If no upstream is set (new branch):
git -C "{worktree_path}" push -u origin "{branch}"
If upstream exists:
git -C "{worktree_path}" push origin "{branch}"
Never rely on implicit current directory branch for pushes in multi-worktree workflows.
If push is rejected because remote has new commits:
git -C "{worktree_path}" pull --rebase origin "{branch}"
git -C "{worktree_path}" push origin "{branch}"
If there are conflicts during rebase:
If there are no commits to push, inform the user that the branch is up to date.
If authentication fails:
gh auth login for GitHubAfter pushing, verify the push succeeded:
git -C "{worktree_path}" log "origin/{branch}" -1 --oneline
Report the pushed commit hash and message to confirm success.
Also report the worktree path used for the push.