Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

review-diff

Sterne1

Forks0

Aktualisiert29. April 2026 um 15:20

Review a git diff for regressions, style violations, complexity, and security issues. Use for cross-tool monitoring — one agent reviews another's 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

gburd

gburd/nix-config

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-diff
description	Review a git diff for regressions, style violations, complexity, and security issues. Use for cross-tool monitoring — one agent reviews another's changes.

Workflow

Show what changed: git -P log --oneline main..HEAD and git -P diff --stat main..HEAD
Review each file: git -P diff main..HEAD -- <file>
Check: correctness, regressions, style, complexity, security, tests
Run tests: cargo test && cargo clippy --all-targets --all-features -- -D warnings
Report findings with file:line references and severity (blocker/warning/nit)

Cross-Tool Usage

Claude makes changes → commit → Kiro runs /review-diff Kiro makes changes → commit → Claude reviews the branch

Mehr aus diesem Repository

gleiches Repository

aws-benchmark

gburd/nix-config

Run performance benchmarks on AWS EC2 (bare-metal or regular instances) with a reproducible launch → tune → measure → terminate workflow. Use for ANY AWS benchmarking — CPU/memory/IO/database/application, NUMA-related or not: choosing + launching an instance, one-time key-pair/security-group setup, OS kernel tuning (hugepages, governor, THP, NUMA balancing), EBS provisioning, A/B methodology, collecting results, and (critically) terminating the instance when done so it stops costing money. Triggers on: "benchmark on AWS/EC2", "bare-metal EC2", "launch an instance to test", "A/B benchmark", "clock sweep / NUMA benchmark", "pgbench/HammerDB on EC2". For the PostgreSQL-buffer-manager clock-sweep specifics, this pairs with the pg-numa-benchmark skill (which uses this one for the AWS substrate).

2026-07-081

pg-numa-benchmark

gburd/nix-config

Run PostgreSQL clock sweep benchmarks on bare-metal EC2 instances. Covers AWS setup, instance launch (r8i.metal-96xl / m6i.metal), OS tuning, PG build (stock + patched), pgbench A/B testing, HammerDB TPC-C, and result collection. Use when benchmarking PostgreSQL buffer manager changes on NUMA hardware. The generic AWS benchmarking substrate (launch/tune/A-B/terminate) is in the aws-benchmark skill; this layers the PostgreSQL specifics on top.

2026-07-081

nix-agent-configs

gburd/nix-config

Hard-won lessons for working on the Nix-managed AI agent configs in modules/home-manager/ai/ (the Bedrock-backed agents pi, claude, maki, hermes, codex, plus kiro-cli, and the LiteLLM proxy). Use this skill ONLY when editing files under modules/home-manager/ai/ or debugging agent auth/telemetry/model routing. Covers: telemetry-off enforcement, thinking-effort ceilings, the two Bedrock auth paths (bearer vs SigV4), model-reachability verification, patching pipx/venv tools, and the CI expectations for this repo. Triggers on: editing modules/home-manager/ai, "LiteLLM proxy", "Bedrock auth", "agent telemetry", "thinking effort", "kiro-cli config".

2026-07-031

release-tagging

gburd/nix-config

Date-based release tagging conventions for this maintainer's personal repos (nix-config and other single-author repos). Use this skill ONLY when actually cutting a release or creating/pushing a git tag — the commit→push→tag→push-tag flow, the vYYYY.MM.DD[.N] format, and the deliberate maintainer exceptions to the "never push to main / never force-push" rules. Triggers on: "tag a release", "cut a release", "ship this", "create a tag", "vYYYY.MM.DD".

2026-07-031

subagent-teams

gburd/nix-config

How to run coordinated sub-agent teams (worker → reviewer → re-reviewer) and the Bedrock model-dispatch rules for sub-agents. Use this skill ONLY when spawning/dispatching sub-agents (e.g. Pi's Agent tool, parallel task fan-out) or debugging a sub-agent that dies instantly. Triggers on: "sub-agent", "subagent", "dispatch agents", "parallel agents", "Agent tool", "sub-agent finished in <2s / 0 tool uses".

2026-07-031

postgresq

gburd/nix-config

Research the PostgreSQL community via the agora MCP server (https://pg.ddx.io/mcp/). Use when investigating PostgreSQL internals or extension development, reviewing or writing patches, understanding historical design decisions, finding related prior art, or tracing a feature through 76k+ pgsql-hackers messages and the upstream/master git history.

2026-05-261

name	review-diff
description	Review a git diff for regressions, style violations, complexity, and security issues. Use for cross-tool monitoring — one agent reviews another's changes.

Workflow

Show what changed: git -P log --oneline main..HEAD and git -P diff --stat main..HEAD
Review each file: git -P diff main..HEAD -- <file>
Check: correctness, regressions, style, complexity, security, tests
Run tests: cargo test && cargo clippy --all-targets --all-features -- -D warnings
Report findings with file:line references and severity (blocker/warning/nit)

Cross-Tool Usage

Claude makes changes → commit → Kiro runs /review-diff Kiro makes changes → commit → Claude reviews the branch