agentleFS
Sign inStart free
kaeawckaeawc/auto-mobile/skills/push-my-prs/SKILL.md

push-my-prs

Skill56 starsChanged 35 days agoApache-2.0View on GitHub

Use this workflow skill to iterate through multiple open PRs authored by the current user, address feedback and CI issues, and push follow-up fixes across the set.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 4 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

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

    line 10
  2. Very specific:

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

    line 11
  3. Distinctive:

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

    line 18
  4. Distinctive:

    Commit and push only when there are real changes.

    line 21
  5. Very specific:

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

    line 26
  6. Distinctive:

    Prefer repo validations and scripts over ad hoc commands.

    line 27
  7. Very specific:

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

    line 28
  8. Distinctive:

    Leave ambiguous comments unresolved and note them in the summary.

    line 29
  9. Very specific:

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

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 failures locally with the lightest relevant validation.
  6. Resolve review threads only when the underlying issue is actually addressed.
  7. Commit and push only when there are real changes.
  8. Re-enable automerge if appropriate.

Repo Rules

  • Use github-cli, push-pr, 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/.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free