agentleFS
storybookjsstorybookjs/storybook/.agents/skills/check-pr/SKILL.md

check-pr

Skill92k starsChanged 5 days agoMITView on GitHub

Waits for a PR's checks and reviews to finish, then reports the unresolved review threads, the failing checks and the gaps in the PR description. Use when the user asks to check a PR, whether a PR is ready, or what the Greptile review found.

12 other projects use a version of this.

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 2 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 1 mentionOct 2026: 2 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the storybookjs/storybook repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about storybookjs/storybook

The biggest 5 of 89 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 89

Talked about on Stack Overflow, YouTube, GitHub, Bluesky and Hacker News (89 times).

On Stack Overflow · 30

25 more on Stack Overflow

On YouTube · 25

20 more on YouTube

On GitHub · 19

14 more on GitHub

On Bluesky · 13

8 more on Bluesky

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 11 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:

    Find the PR: Use the number the user gave, else the PR of the current branch: gh pr view --json number -q .number.

    line 16

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

Check PR

Reports what is left on a pull request in storybookjs/storybook. It changes nothing. To act on the review threads, use handle-pr-comments.

queries.md has the commands and GraphQL queries for the steps below.

Steps

  1. Find the PR. Use the number the user gave, else the PR of the current branch: gh pr view --json number -q .number.
  2. Wait for the checks. Poll statusCheckRollup every 30 seconds until no check is pending or in progress. Wait for "Greptile Review" too, when Greptile reviews the head commit. CI runs only when the PR has a ci:* label (see Pull requests), so a PR without one has few checks.
  3. Collect. For each area, list what needs action:
    • Checks: each failing check and the reason. Danger checks the title, the labels and the "Manual testing" section; see Pull requests.
    • Review threads: each unresolved thread, with its author, file and line. Use GraphQL, because only GraphQL gives a thread's id and whether it is resolved.
    • PR comments: each comment on the PR itself (comments in gh pr view) that asks for something and has no answer yet, from humans and bots.
    • Greptile summary: Greptile edits one summary comment on each review. Read its latest version (newest updated_at), with the confidence score and the findings.
    • Description: placeholders, an empty "Manual testing" section, and "How to review" links to commits that are no longer on the branch.
  4. Report. One table with these columns: area, item, author, and status. The status is one of: needs action, for information, or already fixed by a later commit. Put human comments before bot comments. End with the Greptile confidence score and the number of items that need action.

Done when all checks are finished and each unresolved thread is in the table.

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.