agentleFS
Sign inStart free
hmj1026hmj1026/dhpk/skills/pr-summary/SKILL.md

pr-summary

Skill2 starsChanged 6 days agoMITView on GitHub

Summarize accessible open GitHub pull requests from structured gh JSON, filtering bots and grouping results by ticket. Use for a read-only PR status report. Not for: changing PR state, reviewing code, merging, or closing PRs. Output: grouped Markdown written to /tmp/pr-summary.md and displayed for copying.

20 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use benchmark, explain and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dragonflydbSkill

    benchmark

    Benchmark Dragonfly (and compare against Valkey/Redis) on local or remote cloud instances, then produce a performance + memory report with charts and a raw-data appendix. Use this whenever the user runs /benchmark, or asks to benchmark / load-test / measure throughput, QPS, latency, or memory efficiency of Dragonfly or another Redis-compatible server, to compare Dragonfly vs Valkey or Redis, or to generate a benchmark report. Trigger it even when the user just describes the goal ("see how fast Dragonfly is on this box", "compare memory per key vs Valkey") without saying the word "benchmark".

    Also in 3 projects that use this

  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • VercelSkill

    investigate

    Investigate an issue report, or analyze the constraints of a proposed change, with strict, evidence-driven diagnosis.

    Also in 3 projects that use this

  • SentrySkill

    onboard

    Onboard a service to sentry-options. Use when integrating a new service, creating schemas, or setting up the multi-repo sentry-options workflow.

    Also in 3 projects that use this

  • AWSSkill

    retro

    Conduct a retrospective on a coding session.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 0

    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. Very specific:

    Run in the consumer repository and preserve --author <user> and --label <label>.

    line 15

“Common” is measured: kept by at least 6 in 10 of the 16 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 Summary

Workflow

Run in the consumer repository and preserve --author <user> and --label <label>. Resolve the repository with gh repo view, then query open PRs with gh pr list --json ...; consume structured JSON rather than scraping terminal formatting. Stop when gh is unavailable, the repository query fails, or the PR query fails.

Filter bot-authored PRs, group the remaining records by ticket ID (including stacked PR annotations), format the report, write the same report to /tmp/pr-summary.md, and display it with copy instructions. The exact JSON fields and grouping rules are in references/workflow.md. This workflow never changes GitHub state.

When NOT to Use

  • A PR must be created, edited, merged, closed, or labeled.
  • A code review or merge-readiness verdict is requested.
  • gh repository credentials or access are unavailable.

Output

Formatted open-PR groups with ticket IDs and stacked-PR annotations, plus the path /tmp/pr-summary.md and copy instructions. An empty result is a valid report. Query or report-write failures are terminal UNAVAILABLE/FAIL results and must be surfaced.

Verification

  • Repository and PR data came from successful structured gh JSON calls.
  • --author/--label filters were preserved and bot PRs were handled.
  • Every included PR appears in exactly one ticket group (or an explicit unassigned group).
  • /tmp/pr-summary.md exists and matches the displayed report.

References

  • references/workflow.md — gh fields, filters, bot exclusion, ticket grouping, and report format.

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