Pushes local branches, creates/updates PRs, and links them to Linear issues.
Install
mkdir -p .claude/skills/push-robinbeier && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12793" && unzip -o skill.zip -d .claude/skills/push-robinbeier && rm skill.zipInstalls to .claude/skills/push-robinbeier
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Push the current issue branch, create or update the GitHub pull request, linkKey capabilities
- →Push the current branch to origin safely
- →Create a new GitHub pull request if missing
- →Update an existing GitHub pull request
- →Attach the PR to the Linear issue tracker
- →Move the Linear issue to 'In Review' or 'Ready to Merge' state
- →Fill PR body using a repository template
How it works
The skill automates the process of pushing a branch, creating or updating a GitHub pull request, and linking it to a Linear issue while updating its status.
Inputs & outputs
When to use push
- →Push branch and create PR
- →Update PR body
- →Link PR to issue
About this skill
Push
Use when the current branch is ready to publish or when review fixes must be pushed to an existing PR. Keep the state and exact-head invariants in the agent workflow contract authoritative.
Steps
- Confirm the current branch and a clean worktree; finalize intended local edits with $commit. Run the scoped validation selected by WORKFLOW.md; do not rerun a passing check gratuitously.
- Push with upstream tracking when needed:
git push -u origin HEAD. - If the push is rejected because the branch is stale or non-fast-forward,
follow $pull, then push again. If history was
intentionally rewritten,
--force-with-leaseis the only permitted force option. Surface authentication or other push failures as failures. - Ensure a PR exists. Create or update it as needed; if its prior PR is
closed or merged, use a fresh branch and PR. Fill every section of the
current PR template and remove
placeholders before
gh pr createorgh pr edit. - When an associated Linear issue exists, attach the published PR, move the
issue to
In Review, and update the single## Codex Workpadcomment with validation, posture, and next action. Follow $linear for those operations and WORKFLOW.md for the workpad. - Reply with the published PR URL. Creating a PR does not authorize merging.
Any push after CI or review evidence makes that landing evidence stale. Return
the issue to In Review and follow the exact-head and independent-review rules
in WORKFLOW.md. Keep the PR URL
on the Linear issue, not in the workpad.
If the correct diff is already present and validated, publish it without reopening analysis. Standard review and publication do not require a separate CLI login; use the canonical review expectations.
When not to use it
- →When the worktree is not clean before pushing
- →When the branch is tied to a closed or merged PR and needs to be reopened
- →When push fails for authentication or permissions issues
Limitations
- →The skill requires a clean worktree before pushing.
- →It assumes the existence of a `.github/pull_request_template.md` for PR body generation.
- →It does not handle authentication or permission failures for Git push.
How it compares
This skill simplify the PR creation and Linear issue management workflow, automating multiple steps that would otherwise require manual execution and coordination between Git, GitHub, and Linear.
Compared to similar skills
push side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| push (this skill) | 0 | 4mo | Review | Beginner |
| pr | 0 | 2mo | Review | Intermediate |
| proof-of-work | 1 | 8mo | No flags | Intermediate |
| resolve-conflicts | 81 | 10mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
pr
meshtastic
Push the current branch and open a draft PR for Meshtastic-Android the repo way — baseline verified first, body drafted per .github/copilot-pull-request-instructions.md (WHY-first, categorized changes), screenshots embedded via commit-pinned raw URLs. Use whenever work is ready to go up as a PR.
proof-of-work
MadAppGang
Proof artifact generation patterns for task validation. Covers screenshots, test results, deployments, and confidence scoring.
resolve-conflicts
antinomyhq
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
git-commits
bonny
Create well-structured git commits in logical chunks following best practices
git-advanced-workflows
wshobson
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.