Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

jkreview

Sterne6

Forks0

Aktualisiert21. Juni 2026 um 14:58

Review a GitHub PR. Provide a URL to review without checking it out locally, or omit the URL if the branch is already checked out.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

johnkerl

johnkerl/dotfiles

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	jkreview
description	Review a GitHub PR. Provide a URL to review without checking it out locally, or omit the URL if the branch is already checked out.

If a GitHub PR URL is provided: Use gh pr view <url> for metadata and gh pr diff <url> for the diff. Do not check out the branch. Review purely from the diff and any linked context (description, comments).

If no URL is provided: Assume the current branch is the PR under review. Use git diff $(git merge-base HEAD main)...HEAD (detect the right base), plus gh pr view if a PR exists.

Review as a thoughtful senior engineer doing a real code review:

Is the approach sound, or is there a better way?
Bugs, edge cases, error handling gaps
Security or performance concerns
Clarity: would you understand this in six months?
Anything that would block you from approving

Give specific file/line feedback. Separate blocking issues from suggestions. End with a clear statement: approve, approve-with-comments, or request-changes — and why.

Mehr aus diesem Repository

gleiches Repository

jkmdfmt

johnkerl/dotfiles

Format up an LLM answer into consistent personal markdown style — sentence-case headings and bullet lead-ins, plain dash bullets, no emoji, straight em-dash handling, italics not bold, optional 100-col wrap. Pass a file path to clean in place, or paste raw text to get the cleaned result back in chat.

2026-07-036

jkloop5

johnkerl/dotfiles

A decorator on top of /loop with 5-minute timer and autocancel

2026-07-026

jkaddrcom

johnkerl/dotfiles

Action GitHub PR review comments. Provide a PR URL to fix all open comments, or a specific comment URL to fix one.

2026-06-296

jkprereview

johnkerl/dotfiles

Review the current branch's diff from a skeptic's perspective before pushing. Optional arg selects the reviewer persona.

2026-06-216

jksubmit

johnkerl/dotfiles

Commit, push, and open a draft PR with a written description. Use when ready to share work in progress for review.

2026-06-216

jksync

johnkerl/dotfiles

Sync the current branch with the repo's primary branch (main, master, preprod, etc). Pulls primary, switches back, merges in, pushes.

2026-06-216

name	jkreview
description	Review a GitHub PR. Provide a URL to review without checking it out locally, or omit the URL if the branch is already checked out.

If no URL is provided: Assume the current branch is the PR under review. Use git diff $(git merge-base HEAD main)...HEAD (detect the right base), plus gh pr view if a PR exists.

Review as a thoughtful senior engineer doing a real code review:

Is the approach sound, or is there a better way?
Bugs, edge cases, error handling gaps
Security or performance concerns
Clarity: would you understand this in six months?
Anything that would block you from approving

Give specific file/line feedback. Separate blocking issues from suggestions. End with a clear statement: approve, approve-with-comments, or request-changes — and why.