Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

code-review

Sterne6

Forks3

Aktualisiert3. Januar 2026 um 00:30

Comprehensive code review checklist. Use when asked to review code, PRs, pull requests, or before committing changes.

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

jaeyeom

jaeyeom/experimental

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	Comprehensive code review checklist. Use when asked to review code, PRs, pull requests, or before committing changes.
allowed-tools	Bash(git diff:), Bash(git log:), Bash(git show:), Bash(gh:), Bash(make lint:*), Read, Grep, Glob

Code Review Skill

Key Focus Areas

Code Quality

DRY (Don't Repeat Yourself): Extract duplicated code.
Error Handling: Ensure proper error wrapping, propagation, and logging.
- Go: Do not log and bubble up (avoids duplicate logs).
Resource Cleanup: Use defer (Go) or RAII patterns (C++).
Clear Naming: meaningful names for functions and variables.
Simplicity: Prioritize simple solutions over complex ones.
Organization: Keep files concise (200-300 lines).

Language-Specific Checks

Go: Goroutine safety, error handling, interface usage.
Python: PEP 8, type hints.
C++: RAII, const correctness.
Protobuf: Backward compatibility.

Best Practices

Be constructive and specific.
Focus on significant issues, not nitpicks.
Acknowledge good practices.

Mehr aus diesem Repository

gleiches Repository

spacemacs

jaeyeom/experimental

Edit the Spacemacs .spacemacs configuration, add packages/layers, write elisp hooks, and manage custom elisp in private/local. Use when working with spacemacs/.spacemacs, Emacs Lisp for the user's config, Spacemacs layers or keybindings, or elisp packages in ~/.config/emacs/private/local/. Also triggers for Claude Code Emacs integration (claude-code.el hooks, alert.el, my-attention.el).

2026-04-026

ansible-dev-setup

jaeyeom/experimental

Generate and manage cross-platform Ansible playbooks for development environment setup across macOS, Linux, and Termux. Use when working with development environment automation, package installation configuration, or Ansible playbook generation.

2026-01-216

claude-code-mechanism-selector

jaeyeom/experimental

Helps choose the right Claude Code extension mechanism (slash commands, skills, subagents, or hooks) for a given use case. Use when discussing how to extend Claude Code, automate workflows, or implement custom functionality.

2026-01-016

name	code-review
description	Comprehensive code review checklist. Use when asked to review code, PRs, pull requests, or before committing changes.
allowed-tools	Bash(git diff:), Bash(git log:), Bash(git show:), Bash(gh:), Bash(make lint:*), Read, Grep, Glob

Code Review Skill

Key Focus Areas

Code Quality

DRY (Don't Repeat Yourself): Extract duplicated code.
Error Handling: Ensure proper error wrapping, propagation, and logging.
- Go: Do not log and bubble up (avoids duplicate logs).
Resource Cleanup: Use defer (Go) or RAII patterns (C++).
Clear Naming: meaningful names for functions and variables.
Simplicity: Prioritize simple solutions over complex ones.
Organization: Keep files concise (200-300 lines).

Language-Specific Checks

Go: Goroutine safety, error handling, interface usage.
Python: PEP 8, type hints.
C++: RAII, const correctness.
Protobuf: Backward compatibility.

Best Practices

Be constructive and specific.
Focus on significant issues, not nitpicks.
Acknowledge good practices.