Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

code-review

Sterne4

Forks0

Aktualisiert14. Juli 2026 um 17:17

Use when reviewing code — a diff, a pull request, or a peer agent's output. Gives the review order (security, correctness, test coverage, conventions) and the comment format (BLOCKING / SUGGESTION / NITPICK).

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

dangtrivan15

dangtrivan15/choruskube

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	code-review
description	Use when reviewing code — a diff, a pull request, or a peer agent's output. Gives the review order (security, correctness, test coverage, conventions) and the comment format (BLOCKING / SUGGESTION / NITPICK).

Code Review

You perform structured, actionable code reviews.

Review order (always follow this sequence)

Security — auth bypasses, injection vectors, secret exposure, insecure defaults
Correctness — logic errors, edge cases, null/undefined handling, error propagation
Test coverage — are new code paths covered? do tests exercise the contract, not the implementation?
Style & conventions — naming, formatting, adherence to the project's CLAUDE.md conventions

Format

Group comments by file, then by severity: BLOCKING → SUGGESTION → NITPICK
For each BLOCKING comment, state what breaks and propose the exact fix
For SUGGESTION, explain the trade-off
Do not comment on auto-fixable style (formatter handles it)
End with a one-paragraph summary: overall assessment, key risks, recommended action

Mehr aus diesem Repository

gleiches Repository

claude-md-management

dangtrivan15/choruskube

Use when creating or editing a CLAUDE.md file, or when a change alters conventions that CLAUDE.md documents. Covers what belongs in CLAUDE.md versus CONTRIBUTING.md, the expected structure, and the size limit.

2026-07-144

code-simplifier

dangtrivan15/choruskube

Use when asked to simplify, refactor, or reduce complexity in existing code, or when a change has left code harder to follow. Lists the complexity signals to look for and the rules for refactoring safely.

2026-07-144

feature-dev

dangtrivan15/choruskube

Use when implementing a new feature or a bugfix, before writing implementation code. Enforces a read-first, test-driven, incremental workflow (red, green, refactor, verify) and the rules for not weakening existing tests.

2026-07-144

lsp

dangtrivan15/choruskube

Use before making structural changes to code — renaming a symbol, deleting code, adding an import, or altering a shared DTO or interface. Covers how to establish blast radius before the edit rather than after.

2026-07-144

frontend-design

dangtrivan15/choruskube

Use when writing or modifying code under web-ui/ — React 19, TypeScript, Tailwind, TanStack Query. Covers this project's state, typing, import, component, WebSocket, and graph-rendering conventions plus the checks that must pass before declaring done.

2026-07-144

name	code-review
description	Use when reviewing code — a diff, a pull request, or a peer agent's output. Gives the review order (security, correctness, test coverage, conventions) and the comment format (BLOCKING / SUGGESTION / NITPICK).

Code Review

You perform structured, actionable code reviews.

Review order (always follow this sequence)

Security — auth bypasses, injection vectors, secret exposure, insecure defaults
Correctness — logic errors, edge cases, null/undefined handling, error propagation
Test coverage — are new code paths covered? do tests exercise the contract, not the implementation?
Style & conventions — naming, formatting, adherence to the project's CLAUDE.md conventions

Format

Group comments by file, then by severity: BLOCKING → SUGGESTION → NITPICK
For each BLOCKING comment, state what breaks and propose the exact fix
For SUGGESTION, explain the trade-off
Do not comment on auto-fixable style (formatter handles it)
End with a one-paragraph summary: overall assessment, key risks, recommended action