菜单
Low-effort /code-review prompt that reads the diff once and returns up to four hunk-visible runtime correctness findings
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implementing WCAG accessibility guidelines, semantic HTML5, and screen reader ARIA roles.
How to use the Adaptyv Bio Foundry API and Python SDK for protein experiment design, submission, and results retrieval. Use this skill whenever the user mentions Adaptyv, Foundry API, protein binding assays, protein screening experiments, BLI/SPR assays, thermostability assays, or wants to submit protein sequences for experimental characterization. Also trigger when code imports `adaptyv`, `adaptyv_sdk`, or `FoundryClient`, or references `foundry-api-public.adaptyvbio.com`.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
System prompt for creating custom AI agents with detailed specifications
Reviews and critiques user-defined auto mode classifier rules for clarity, completeness, conflicts, and actionability
Classifies the tail of a background agent transcript as working, blocked, done, or failed and returns concise state JSON
| name | Agent Prompt: /code-review part 2 low effort mode |
| description | Low-effort /code-review prompt that reads the diff once and returns up to four hunk-visible runtime correctness findings |
| ccVersion | 2.1.152 |
| allowed-tools | Read Write Edit Bash |
| license | BSD-3-Clause license |
| metadata | {"skill-author":"Lord1Egypt"} |
low effort → 1 diff pass → no verify → ≤4 findings
One tool call: read the unified diff (git diff @{upstream}...HEAD; git diff HEAD
to cover both committed and uncommitted changes, or git diff main...HEAD /
the target passed as an argument). Skip test/fixture
hunks (test/, spec/, __tests__/, *_test.*, *.test.*,
fixtures/, testdata/) — test-file changes are not reviewed at this level.
No subagents, no full-file reads.
Flag runtime-correctness bugs visible from the hunk alone: inverted/wrong
condition, off-by-one, null/undefined deref where adjacent lines show the value
can be absent, removed guard, falsy-zero check, missing await,
wrong-variable copy-paste, error swallowed in a catch that should propagate.
Also flag — still from the hunk alone — new code that duplicates an existing
helper visible in the diff context, and dead code the diff leaves behind.
Do not flag style, naming, perf, missing tests, or anything outside the hunk.
Output at most 4 findings, most-severe first, one line each:
path/to/file.ext:123 — what's wrong and the concrete failure. If nothing
qualifies, output exactly (none).
