Source profileQuality 71/100Review permissions

dyoshikawa/rulesync/.rulesync/skills/opencode-gpt-review/SKILL.md

opencode-gpt-review

Run the `review-full-pr` skill on another model (github-copilot/gpt-5.4) via opencode, then thoroughly investigate and vet the resulting findings, and present only the valid ones to the user.

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

Decision brief

What it does—and where it fits

Run the review-full-pr skill on another model (github-copilot/gpt-5.4) via opencode, then thoroughly investigate and vet the resulting findings, extract only the valid ones, and present them to the user.

Best for

    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/opencode-gpt-review"
    Safe inspection promptEditorial

    Inspect the Agent Skill "opencode-gpt-review" from https://github.com/dyoshikawa/rulesync/blob/310b711fbe8cffc14debb276ade8a384c2b89083/.rulesync/skills/opencode-gpt-review/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

      1. Run review-full-pr via opencode

      Run the following command to have the github-copilot/gpt-5.4 model execute the review-full-pr skill via opencode.

      --model github-copilot/gpt-5.4: Use the GPT-5.4 model.Run the following command to have the github-copilot/gpt-5.4 model execute the review-full-pr skill via opencode.- --model github-copilot/gpt-5.4: Use the GPT-5.4 model.
    2. 02

      2. Investigate and Vet the Review Results

      For each finding in the review results obtained from opencode, investigate thoroughly using the following steps. Consider using subagents when appropriate.

      Based on the file path and line number in the finding, read the actual code to verify.Also check related context (related functions, classes, settings, etc.) that underlies the finding.Fact check: Does the finding match the actual code (is it not a hallucination)?
    3. 03

      GPT Review Result

      (List only findings judged as valid in the format below. If none, write "None".)

      Review target PR: (PR URL or number)opencode model: github-copilot/gpt-5.4Total findings: N
    4. 04

      Prerequisites

      OpenCode must be installed.

      OpenCode must be installed.If not installed, tell the user it can be installed with curl -fsSL https://opencode.ai/install | bash.OpenCode must be configured to use GitHub Copilot.

    Permission review

    Static risk signals and limitations

    Runs scripts

    medium · line 12

    The documentation asks the agent to run terminal commands or scripts.

    If not configured, tell the user to run `opencode` and use the `/connect` command to authenticate with GitHub Copilot.

    Runs scripts

    medium · line 22

    The documentation asks the agent to run terminal commands or scripts.

    Run the following command to have the github-copilot/gpt-5.4 model execute the review-full-pr skill via opencode.

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score71/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/opencode-gpt-review/SKILL.md
    Commit
    310b711fbe8cffc14debb276ade8a384c2b89083
    License
    MIT
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    GPT Review

    Run the review-full-pr skill on another model (github-copilot/gpt-5.4) via opencode, then thoroughly investigate and vet the resulting findings, extract only the valid ones, and present them to the user.

    Prerequisites

    • OpenCode must be installed.
      • If not installed, tell the user it can be installed with curl -fsSL https://opencode.ai/install | bash.
    • OpenCode must be configured to use GitHub Copilot.
      • If not configured, tell the user to run opencode and use the /connect command to authenticate with GitHub Copilot.

    0. Variable Definitions

    PR_TARGET = the user's request

    If no PR URL or PR number is provided, use the PR associated with the current branch as the review target.

    1. Run review-full-pr via opencode

    Run the following command to have the github-copilot/gpt-5.4 model execute the review-full-pr skill via opencode.

    opencode run \
  --model github-copilot/gpt-5.4 \
  "review-full-pr スキルで ${PR_TARGET} をレビューしてください"
    • --model github-copilot/gpt-5.4: Use the GPT-5.4 model.

    Capture all output from the command.

    2. Investigate and Vet the Review Results

    For each finding in the review results obtained from opencode, investigate thoroughly using the following steps. Consider using subagents when appropriate.

    2-1. Verify the Actual Code at the Finding's Location

    • Based on the file path and line number in the finding, read the actual code to verify.
    • Also check related context (related functions, classes, settings, etc.) that underlies the finding.

    2-2. Judge the Validity of the Finding

    Judge each finding from the following perspectives:

    • Fact check: Does the finding match the actual code (is it not a hallucination)?
    • Impact: Does the reported issue actually have an impact?
    • Context understanding: Is it valid given the project's conventions and architecture?
    • Reproducibility: Can the reported issue actually occur?

    2-3. Classify the Finding

    • Valid: A finding that is confirmed to be a real issue after checking the actual code.
    • Rejected: A hallucination, misunderstanding, or a finding that is not an issue given the project context.

    3. Present the Results

    Output in the following format.

    Overview

    • Review target PR: (PR URL or number)
    • opencode model: github-copilot/gpt-5.4
    • Total findings: N
    • Valid findings: M

    Valid Findings

    (List only findings judged as valid in the format below. If none, write "None".)

    Finding 1: (Title)

    • File: path/to/file.ext:line
    • Problem: (What is the problem)
    • Reason: (Why it is a problem, based on the actual code you verified)
    • Severity: "Must fix before merge" / "Can be deferred"
    • Recommended fix: (Specific fix approach)

    Rejected Findings

    (List rejected findings and the reasons concisely. If none, write "None".)

    • Finding: Reason for rejection

    References

    Alternatives

    Compare before choosing

    Computed 10042,015

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    2026-07-270 platforms
    Computed 1007

    event4u-app/agent-config

    design-intelligence

    Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

    2026-07-280 platforms
    Computed 1007

    event4u-app/agent-config

    existing-ui-audit

    Use BEFORE writing or editing any non-trivial UI — inventories components, design tokens, shadcn primitives, and reusable patterns into state.ui_audit. Hard gate for the ui directive set.

    2026-07-280 platforms
    Computed 1007

    event4u-app/agent-config

    testing-anti-patterns

    Use BEFORE writing/changing tests, adding mocks, or test-only methods on production classes — vs mocking-the-mock, production pollution, partial mocks, and overfit/tautological assertions

    2026-07-280 platforms