review-pr

Sterne33

Forks31

Aktualisiert16. April 2026 um 14:41

Thorough code review of current changes or a specific PR

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

layer-3

layer-3/nitrolite

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	review-pr
description	Thorough code review of current changes or a specific PR
allowed-tools	Bash, Read, Grep, Glob

Review changes for: $ARGUMENTS

Get the diff:
- If $ARGUMENTS is a PR number: gh pr diff $ARGUMENTS
- If no arguments: git diff and git diff --staged for uncommitted changes
For each changed file, check:
- Correctness: Does the logic do what it claims? Any off-by-one errors, race conditions, or wrong assumptions?
- Types: Are TypeScript types accurate and strict? Are Go errors properly handled?
- Security: No exposed secrets, no injection vectors, no reentrancy (contracts), no XSS
- Tests: Are new functions tested? Are edge cases and error paths covered?
- Exports: If public API changed, is the barrel index.ts updated? (sdk-compat: no SSR-unsafe re-exports)
- Docs: If behavior changed, are README/CLAUDE.md/migration docs updated?
- Style: Consistent with existing patterns in the file and project conventions
Categorize findings:
- CRITICAL: Must fix before merge (bugs, security issues, data loss risk)
- WARNING: Should fix (missing tests, poor error handling, incomplete docs)
- SUGGESTION: Nice to have (naming improvements, minor refactors, style tweaks)
Give an overall verdict: APPROVE / REQUEST CHANGES / COMMENT

Mehr aus diesem Repository

gleiches Repository

yellow-settlement-room

layer-3/nitrolite

Yellow Network Protocol app sessions for AI agents - a shared room where several agents pool funds, reallocate off-chain at machine speed, and settle one final split. Use for multiparty settlement among agents. Covers connecting, the funded-account prerequisite, creating a session with participants + weights + quorum, deposit, operate, withdraw, close, and the trust boundary. Grounded in the official @yellow-org/sdk lifecycle example.

2026-07-1533

test

layer-3/nitrolite

Run tests for a specific module or the whole project

2026-04-3033

build-sdk

layer-3/nitrolite

Build SDK packages in the correct dependency order

2026-04-1633

lint

layer-3/nitrolite

Run linters and formatters for the appropriate language

2026-04-1633

typecheck

layer-3/nitrolite

Run TypeScript type checking across SDK packages

2026-04-1633

name	review-pr
description	Thorough code review of current changes or a specific PR
allowed-tools	Bash, Read, Grep, Glob

Review changes for: $ARGUMENTS

Get the diff:
- If $ARGUMENTS is a PR number: gh pr diff $ARGUMENTS
- If no arguments: git diff and git diff --staged for uncommitted changes
For each changed file, check:
- Correctness: Does the logic do what it claims? Any off-by-one errors, race conditions, or wrong assumptions?
- Types: Are TypeScript types accurate and strict? Are Go errors properly handled?
- Security: No exposed secrets, no injection vectors, no reentrancy (contracts), no XSS
- Tests: Are new functions tested? Are edge cases and error paths covered?
- Exports: If public API changed, is the barrel index.ts updated? (sdk-compat: no SSR-unsafe re-exports)
- Docs: If behavior changed, are README/CLAUDE.md/migration docs updated?
- Style: Consistent with existing patterns in the file and project conventions
Categorize findings:
- CRITICAL: Must fix before merge (bugs, security issues, data loss risk)
- WARNING: Should fix (missing tests, poor error handling, incomplete docs)
- SUGGESTION: Nice to have (naming improvements, minor refactors, style tweaks)
Give an overall verdict: APPROVE / REQUEST CHANGES / COMMENT