agentleFS
joris887joris887/exosuit/.claude/skills/pr-status/SKILL.md

pr-status

Skill9 starsChanged 3 months agoMITView on GitHub

Check status of open pull requests and provide options for next steps. Use to review PR status, handle feedback, or merge approved PRs.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check status of your pull requests:

    line 16
  2. Very specific:

    Wait or request review: gh pr edit <number> --add-reviewer <user>

    line 68

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

pr-status

Check status of your pull requests:

Current Open PRs (auto-fetched)

!gh pr list --author @me --state open --json number,title,state,reviewDecision,statusCheckRollup --template '{{range .}}PR #{{.number}}: {{.title}} Review: {{.reviewDecision}} | Checks: {{range .statusCheckRollup}}{{.state}} {{end}} {{end}}' 2>/dev/null || echo "No open PRs or gh not configured"

1. Analyze PR Status

2. For Each Open PR

gh pr view <number> --json state,reviewDecision,statusCheckRollup,mergeable
gh pr checks <number>

3. Status Summary

## PR Status Report

### PR #[number]: [title]
- **Branch**: [branch-name]
- **Review Status**: [Approved/Changes Requested/Pending]
- **Checks**: [Passing/Failing/Pending]
- **Mergeable**: [Yes/No - reason if no]

### Recommended Actions
- [Action based on status]

4. Available Actions

Based on PR status, offer options:

If Approved + Checks Passing:

gh pr merge --squash --delete-branch

If Changes Requested:

  • View review comments: gh pr view <number> --comments
  • Address feedback and push updates

If Checks Failing:

  • View failed checks: gh pr checks <number>
  • Fix issues and push

If Pending Review:

  • Wait or request review: gh pr edit <number> --add-reviewer <user>

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.