Slash Command

/SKILL

Iterates through your open PRs in the current repo, addresses feedback and CI issues, and pushes follow-up fixes across the set.

Git

Github

git-workflow

npx claudepluginhub kaeawc/auto-mobile --plugin auto-mobile

Details

Namespacepush-my-prs/

Prompt Preview

# Push My PRs

Iterate through your open PRs in the current repo and keep them moving.

- Prefer `push-pr` when the task is about the current branch or a single PR.
- Prefer `push-my-prs` only for batch PR maintenance.

## Workflow

1. Get the current GitHub user with `gh api user -q .login`.
2. List open PRs for that author with `gh pr list --author "$GH_USER" --state open`.
3. For each PR, gather CI status, mergeability, review verdicts, unresolved threads, and top-level comments.
4. Check out the PR branch, pull the latest changes, and address actionable feedback.
5. Reproduce CI failure...

Command Content

Other plugins with /SKILL

/fix-pr

Fixes PR issues by gathering review comments, status checks, CI failures; creates task list and applies code changes to the PR branch.

/pr-review

Reviews GitHub PR comments by priority, applies fixes via code edits, commits and pushes changes, verifies CI status, and outputs a markdown summary.

6 tools

majestic-engineer

/pr-review

Responds to GitHub PR review comments for specified PR numbers or all open PRs using agents to address issues, push fixes, and generate summaries.

10 tools

project-toolkit

/SKILL

512

Configures Git user identity and project commit scopes: verifies name/email, initializes git-agent, validates scopes from .git-agent/config.yml, generates .claude/git.local.md.

haiku7 tools

git

/SKILL

512

Launches isolated code-context researcher agent to fetch repo/library context via DeepWiki, Context7, Exa, git clone, or all methods. Accepts repo URL/name and optional --method flag.

code-context

/SKILL

512

Creates a GitHub pull request with automated quality validation, security scanning, issue linking, and compliance checks. Accepts optional description or issue reference.

3 tools

github

Stats

Stars34

Forks0

Last CommitApr 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# Push My PRs Iterate through your open PRs in the current repo and keep them moving. - Prefer `push-pr` when the task is about the current branch or a single PR. - Prefer `push-my-prs` only for batch PR maintenance. ## Workflow 1. Get the current GitHub user with `gh api user -q .login`. 2. List open PRs for that author with `gh pr list --author "$GH_USER" --state open`. 3. For each PR, gather CI status, mergeability, review verdicts, unresolved threads, and top-level comments. 4. Check out the PR branch, pull the latest changes, and address actionable feedback. 5. Reproduce CI failure...

Push My PRs

Iterate through your open PRs in the current repo and keep them moving.

Prefer push-pr when the task is about the current branch or a single PR.

Prefer push-my-prs only for batch PR maintenance.

Workflow

Get the current GitHub user with gh api user -q .login.

List open PRs for that author with gh pr list --author "$GH_USER" --state open.

For each PR, gather CI status, mergeability, review verdicts, unresolved threads, and top-level comments.

Check out the PR branch, pull the latest changes, and address actionable feedback.

Reproduce CI failures locally with the lightest relevant validation.

Resolve review threads only when the underlying issue is actually addressed.

Commit and push only when there are real changes.

Re-enable automerge if appropriate.

Repo Rules

Use github-cli, gh-pr-workflow, check-ci, and validate conventions.

Prefer repo validations and scripts over ad hoc commands.

Never force push unless a rebase made it necessary, and then use --force-with-lease only.

Leave ambiguous comments unresolved and note them in the summary.

Write logs or thread snapshots you need to keep under scratch/.

Push My PRs

Iterate through your open PRs in the current repo and keep them moving.

Prefer push-pr when the task is about the current branch or a single PR.
Prefer push-my-prs only for batch PR maintenance.

Workflow

Get the current GitHub user with gh api user -q .login.
List open PRs for that author with gh pr list --author "$GH_USER" --state open.
For each PR, gather CI status, mergeability, review verdicts, unresolved threads, and top-level comments.
Check out the PR branch, pull the latest changes, and address actionable feedback.
Reproduce CI failures locally with the lightest relevant validation.
Resolve review threads only when the underlying issue is actually addressed.
Commit and push only when there are real changes.
Re-enable automerge if appropriate.

Repo Rules

Use github-cli, gh-pr-workflow, check-ci, and validate conventions.
Prefer repo validations and scripts over ad hoc commands.
Never force push unless a rebase made it necessary, and then use --force-with-lease only.
Leave ambiguous comments unresolved and note them in the summary.
Write logs or thread snapshots you need to keep under scratch/.