New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Pull Request Reviewer for daisyUI

by saadeghi in saadeghi/daisyui

Reviews open pull requests in the daisyUI repository using read-only GitHub data and isolated base-versus-PR checks, then writes a merge verdict report.

MITAuto-check passedDevelopment

Install Pull Request Reviewer for daisyUI

skills CLI
$ npx skills add saadeghi/daisyui --skill pr-review -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install saadeghi/daisyui pr-review --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/saadeghi/daisyui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/pr-review .claude/skills/pr-review && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-review
GitHub stars
43k
Token cost
~766 tokens
SKILL.md length
433 words
Files
2 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
MIT

At a glance

Reviews open pull requests in the daisyUI repository using read-only GitHub data and isolated base-versus-PR checks, then writes a merge verdict report.

  • Works in 8 steps: If the user names a PR, review it.… → Read the PR, linked issues, changed… → Identify the behavior the PR claims to… → …
  • Deciding whether an open daisyUI pull request is safe to merge
  • SKILL.md covers Required agent routing, Boundaries, Workflow and Report
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The workflow is routed through a pr_reviewer custom agent: any other agent hands the whole task to it, and the work stops with a problem report if that agent does not exist. Pull requests are read through the GitHub MCP server with read operations only, the repository is treated as read-only apart from one report file under tmp/pr/, and PR descriptions and comments are treated as claims to verify rather than facts.

You can name a PR, or the agent lists all open ones in saadeghi/daisyui and reviews each separately. It reads linked issues, changed files, checks and the base and head SHAs, makes isolated copies of both in an OS-temporary directory without credentials, and runs the smallest check that shows the old behavior, the new behavior and any regression. A finding is reported only when there is a clear path to a product failure. A PR is marked safe to merge only when its claim is verified, and the head SHA is fetched again before the verdict. A references/report.md file sets the report format.

When your agent uses it

  • Deciding whether an open daisyUI pull request is safe to merge
  • Reviewing every open PR in the repository one by one
  • Checking a PR's claimed fix against the base commit with an isolated run

Example prompts

  • “Review the newest open PR in saadeghi/daisyui and tell me if it is safe to merge.”
  • “Go through all open pull requests and write a report for each one under tmp/pr/.”
  • “Verify that the button focus fix in this PR works on both the base and head commits.”

Requirements

  • The GitHub MCP server
  • A pr_reviewer custom agent
  • A local checkout of saadeghi/daisyui

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. If the user names a PR, review it. Otherwise, list all open PRs in saadeghi/daisyui and
  2. Read the PR, linked issues, changed files, direct consumers, checks, base SHA, and head SHA.
  3. Identify the behavior the PR claims to change and its expected result. A linked issue is not
  4. Create isolated base and head copies in an OS-temporary directory. Use the same environment and
  5. Run the smallest check that proves the base behavior, the PR behavior, and relevant regression
  6. Report a finding only when changed code has a clear path to a product failure or when a required
  7. Mark the PR safe to merge only when the claim is verified, relevant checks pass, and no finding
  8. Re-fetch the PR before the verdict. If the head SHA changed, repeat the affected checks.

What it can do on your machine

Read from SKILL.md and the folder at commit 8c24218. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pull Request Reviewer for daisyUI loads about 766 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 433 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~766
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from saadeghi/daisyui at commit 8c24218, republished under its MIT licence (© saadeghi). 433 words, ~766 tokens.

Download SKILL.mdSave it as .claude/skills/pr-review/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
pr-review
description
Review one or all open pull requests in saadeghi/daisyui with read-only GitHub data and isolated base-versus-PR checks. Use when Codex must verify a PR, find concrete regressions, decide whether it is safe to merge, and write a concise report under tmp/pr/.
metadata.internal
true

PR Reviewer

Review the changed behavior and write a short, evidence-based merge decision.

Required agent routing

  • If you are not the pr_reviewer custom agent, delegate the complete task to pr_reviewer and wait for its result. Tell the agent to use this skill. Do not review the PR in the current agent.
  • If you are the pr_reviewer custom agent, perform this workflow directly. Do not delegate it again.
  • If pr_reviewer is not available, stop and report the problem.

Boundaries

  • Use the GitHub MCP server for GitHub data. Use read operations only.
  • Treat the repository as read-only except for tmp/pr/pr-<number>.md.
  • Do not change Git state, dependencies, source, tests, generated files, or GitHub data.
  • Inspect PR code before you run it. Run PR code only in an OS-temporary copy with no credentials.
  • Test the exact base and head SHAs. Do not use the current working tree as a substitute.
  • Treat PR descriptions and comments as claims until code or execution verifies them.
  • Report only observed facts. Do not report generic or theoretical risks.

Workflow

  1. If the user names a PR, review it. Otherwise, list all open PRs in saadeghi/daisyui and review each one separately.
  2. Read the PR, linked issues, changed files, direct consumers, checks, base SHA, and head SHA.
  3. Identify the behavior the PR claims to change and its expected result. A linked issue is not required.
  4. Create isolated base and head copies in an OS-temporary directory. Use the same environment and inputs for both.
  5. Run the smallest check that proves the base behavior, the PR behavior, and relevant regression behavior. Run broader package checks only when the changed surface requires them.
  6. Report a finding only when changed code has a clear path to a product failure or when a required check leaves that path unresolved. Include its impact, evidence, and reproduction or failed check.
  7. Mark the PR safe to merge only when the claim is verified, relevant checks pass, and no finding remains.
  8. Re-fetch the PR before the verdict. If the head SHA changed, repeat the affected checks. Use the current verified PR state for the report's frontmatter status. Use merged for a merged PR, closed for a PR closed without merge, and open for an open PR.
Show full SKILL.md (59 more words)Show less

Report

Read references/report.md. Write one report per PR to tmp/pr/pr-<number>.md. Include YAML frontmatter with status. Update the status in an existing report instead of creating a duplicate. Keep the PR state separate from the merge decision.

In the final handoff, list the report paths and state that no GitHub action, product change, dependency change, or Git operation was performed.

© saadeghi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .agents/skills/pr-review of saadeghi/daisyui.

  • SKILL.md
  • references/report.md

Open the folder on GitHubat commit 8c24218

Compare with similar skills

Pull Request Reviewer for daisyUI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pull Request Reviewer for daisyUI compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pull Request Reviewer for daisyUI this skillsaadeghi/daisyui43k—~766Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
GitHub Review Iterationprisma/orm48k—~2.2kAutomated safety check: PassApache-2.0
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0
PR Finalize Reviewmicrosoft/garnet12k—~3.1kAutomated safety check: PassMIT
Fastlane Pull Request Reviewfastlane/fastlane42k—~550Automated safety check: PassMIT

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • GitHub Review Iteration

    prisma/orm

    Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed

  • PR Finalize Review

    microsoft/garnet

    Official

    Checks that a pull request's title and description match its implementation and reviews the code for Garnet best practices, reporting findings without posting them.

    12k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Fastlane Pull Request Review

    fastlane/fastlane

    Reviews a fastlane pull request against its linked issue and the project guides, separating blocking from non-blocking findings and handling vulnerabilities privately.

    42k GitHub stars~550 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Pull Request Babysitter

    thedotmack/claude-mem

    Keeps watching a pull request, fixing real review and CI problems and resolving stale threads, until it is clean and ready to merge.

    99k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from saadeghi/daisyui

  • Bug Finder for daisyUI

    saadeghi/daisyui

    Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.

    43k GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • DaisyUI Component Library

    saadeghi/daisyui

    Official daisyUI skill for Tailwind CSS projects, routing to install, usage, configuration, color and per-component guides before writing any HTML or JSX with its classes.

    43k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • DaisyUI 5 Color Rules

    saadeghi/daisyui

    Rules for using daisyUI 5's semantic color names, such as primary and base-100, so interfaces stay readable across themes.

    43k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Styling Rules for daisyUI 5

    saadeghi/daisyui

    Rules for styling HTML with daisyUI 5 class names first, falling back to Tailwind utilities only when needed, and avoiding unnecessary custom CSS or default color variants.

    43k GitHub stars~846 tokensUpdated yesterday
    Auto-check passed

  • daisyUI 5 Installation

    saadeghi/daisyui

    Installation instructions for daisyUI 5 with Tailwind CSS 4: the npm setup, CSS plugin lines, CDN usage and pointers to framework-specific guides.

    43k GitHub stars~967 tokensUpdated yesterday
    Auto-check passed

  • daisyUI 5 Configuration

    saadeghi/daisyui

    Configuration options for daisyUI 5

    43k GitHub stars~352 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Pull Request Reviewer for daisyUI

What does Pull Request Reviewer for daisyUI do?

Reviews open pull requests in the daisyUI repository using read-only GitHub data and isolated base-versus-PR checks, then writes a merge verdict report. The workflow is routed through a pr_reviewer custom agent: any other agent hands the whole task to it, and the work stops with a problem report if that agent does not exist. Pull requests are read through the GitHub MCP server with read operations only, the repository is treated as read-only apart from one report file under tmp/pr/, and PR descriptions and comments are treated as claims to verify rather than facts.

When should I use Pull Request Reviewer for daisyUI?

Pull Request Reviewer for daisyUI fits situations like: deciding whether an open daisyUI pull request is safe to merge; reviewing every open PR in the repository one by one; checking a PR's claimed fix against the base commit with an isolated run.

How do I install Pull Request Reviewer for daisyUI in Claude Code?

Run `npx skills add saadeghi/daisyui --skill pr-review -a claude-code`. Or copy the skill folder (.agents/skills/pr-review in saadeghi/daisyui) into .claude/skills/pr-review in your project. Claude Code loads it when a task matches its description.

How do I install Pull Request Reviewer for daisyUI in Codex?

Run `npx skills add saadeghi/daisyui --skill pr-review -a codex`. Or copy the skill folder (.agents/skills/pr-review in saadeghi/daisyui) into .agents/skills/pr-review in your project. Codex loads it when a task matches its description.

Can I use Pull Request Reviewer for daisyUI in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add saadeghi/daisyui --skill pr-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-review, .gemini/skills/pr-review, .github/skills/pr-review and .opencode/skills/pr-review in your project.

What does Pull Request Reviewer for daisyUI need to run?

SKILL.md names no scripts, command-line tools or credentials: Pull Request Reviewer for daisyUI is instructions for the agent only. Our summary lists: The GitHub MCP server; A pr_reviewer custom agent; A local checkout of saadeghi/daisyui.

Does Pull Request Reviewer for daisyUI access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Pull Request Reviewer for daisyUI safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pull Request Reviewer for daisyUI use?

Pull Request Reviewer for daisyUI is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pull Request Reviewer for daisyUI use?

About 766 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 337 tokens, read only when the agent opens those files.

What are the alternatives to Pull Request Reviewer for daisyUI?

Skills that share tags, products or a category with Pull Request Reviewer for daisyUI: PR Babysitter (openinterpreter/openinterpreter, 69k stars), GitHub Review Iteration (prisma/orm, 48k stars), PR Review State Fetch (prisma/orm, 48k stars) and PR Finalize Review (microsoft/garnet, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pull Request Reviewer for daisyUI?

saadeghi (a GitHub user) maintains it in saadeghi/daisyui, which has 42,562 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 2026.

Source: saadeghi/daisyui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.