Source profileQuality 73/100

dyoshikawa/rulesync/.rulesync/skills/review-pr/SKILL.md

review-pr

Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill".

Source repository stars
1,263
Declared platforms
0
Static risk flags
0
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Execute the following in parallel:

Best for

  • Use when the user wants to review a PR, check PR code changes, or audit a pull request.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/dyoshikawa/rulesync --skill ".rulesync/skills/review-pr"
Safe inspection promptEditorial

Inspect the Agent Skill "review-pr" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/review-pr/SKILL.md at commit 310b711fbe8cffc14debb276ade8a384c2b89083. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    After the Review: Check GitHub Actions Workflows

    After completing the content review, check the status of the GitHub Actions workflows for $targetpr (for example, using gh pr checks or gh run list).

    Report the status of every workflow run to the user, including runs that are still in progress.For each failing workflow, also report:The likely cause of the failure (based on the relevant logs or job output).
  2. 02

    Important: Do Not Switch the Local Branch

    Execute the following in parallel:

    Do NOT check out, switch, or otherwise move the local branch (e.g., git checkout, git switch, gh pr checkout).To inspect the PR's changes, use git and gh commands that read remote state without moving the working tree. For example:gh pr view $targetpr to read PR metadata and description.
  3. 03

    Reporting Rules

    Assign a severity level to each finding: low, mid, high, or critical.

    Assign a severity level to each finding: low, mid, high, or critical.Assign a sequential number to each finding (e.g., 1, 2, 3, ...).- Assign a severity level to each finding: low, mid, high, or critical. - Assign a sequential number to each finding (e.g., 1, 2, 3, ...).

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score73/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars1,263SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
dyoshikawa/rulesync
Skill path
.rulesync/skills/review-pr/SKILL.md
Commit
310b711fbe8cffc14debb276ade8a384c2b89083
License
MIT
Collected
2026-07-28
Default branch
main
View the original SKILL.md

target_pr = the user's request

If target_pr is not provided, use the PR of the current branch.

Important: Do Not Switch the Local Branch

  • Do NOT check out, switch, or otherwise move the local branch (e.g., git checkout, git switch, gh pr checkout).
  • To inspect the PR's changes, use git and gh commands that read remote state without moving the working tree. For example:
    • gh pr view $target_pr to read PR metadata and description.
    • gh pr diff $target_pr to read the diff.
    • gh pr view $target_pr --json files or gh api to list changed files.
    • git fetch origin pull/<PR_NUMBER>/head:refs/remotes/origin/pr-<PR_NUMBER> and git diff origin/main...origin/pr-<PR_NUMBER> if a local read-only ref is needed.
  • When invoking subagents, explicitly instruct them that switching the local branch is forbidden and that they must inspect changes via git/gh commands only.

Execute the following in parallel:

  • Call code-reviewer subagent to review the code changes in $target_pr. Pass along the rule that the local branch must not be switched and that diffs must be obtained via git/gh commands.
  • Call security-reviewer subagent to review the security issues in $target_pr. Pass along the rule that the local branch must not be switched and that diffs must be obtained via git/gh commands.

Integrate and report the execution results from each subagent. Additionaly, please output PR number in the result so that the user can easily find the PR.

Reporting Rules

  • Assign a severity level to each finding: low, mid, high, or critical.
  • Assign a sequential number to each finding (e.g., #1, #2, #3, ...).

After the Review: Check GitHub Actions Workflows

After completing the content review, check the status of the GitHub Actions workflows for $target_pr (for example, using gh pr checks or gh run list).

  • Report the status of every workflow run to the user, including runs that are still in progress.
  • For each failing workflow, also report:
    • The likely cause of the failure (based on the relevant logs or job output).
    • Candidate solutions or next steps to resolve it.

Alternatives

Compare before choosing

Computed 977

event4u-app/agent-config

code-review

Use when the user says "review this", "check my code", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards.

2026-07-280 platforms
Computed 93234,327

affaan-m/ECC

intent-driven-development

Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare implementation requirements for another agent, or make a complex request testable. Do not trigger for trivial edits, straightforward fixes, active debugging, code review, or implementation requests whose acceptance conditions

2026-07-270 platforms
Computed 92165

JasonColapietro/suede-creator-skills

suede-workflow-skills

Umbrella workflow for 67 public skills: Full Send, copy, design, code review, SEO, launch packaging, MCP QA, iOS and Android app shipping, and creator workflows. Loads the full public skill pack.

2026-07-280 platforms
Computed 927

event4u-app/agent-config

git-workflow

Use when working with Git — branch naming, commit messages, PR creation, rebasing, or the code review process — even when the user says 'push this' or 'merge the branch' without naming Git.

2026-07-280 platforms