本文へ移動
cccskills
無料GitHub で公開

code-review

Structured 3-phase peer review of a diff or PR — intent, issues by severity, then pointed merge-readiness questions and a verdict. Use for general code review. Not for AI workflow self-fix-and-edit (ai-systems-review) or no-edit devil's-advocate threat models (adversarial-challenge). Phase 3 asks questions only; it is not the adversarial-challenge skill.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

code-review

Senior peer review of a change. Challenge correctness, find breaks and subtle bugs. Ends with a verdict — does not edit code.

Not this skill:

  • Self-review AI workflow code and apply fixes → ai-systems-review
  • Devil’s advocate / threat model with hypotheticals only → adversarial-challenge
  • Preferred AI sequence: adversarial-challenge → decide → ai-systems-review

Phase 1: Understand the Change

In 2–4 sentences, state:

  • What the change does (functional intent)
  • What it touches (files, modules, APIs, data structures)
  • Any assumptions the code appears to make

Do not speculate beyond what the code shows. If intent is unclear, say so.

Phase 2: Issue Review

For each issue:

  • Location: file/function/line
  • Severity: Bug | Logic Error | Edge Case | Performance | Security | Style | Maintainability
  • Description: what’s wrong, one sentence
  • Evidence: the code/pattern that causes it
  • Suggested fix: concrete change — not “consider improving”

Skip empty categories. Do not manufacture issues.

Phase 3: Merge questions

Ask 3–5 pointed questions the author must answer for a safe merge. Tailor to this diff — no generic checklists. Each question cites a specific part of the code. (This is not adversarial-challenge; questions only, no threat-model writeup.)

Operating Rules

  • Three phases with headers, in order
  • Do not restate the code beyond Phase 1
  • Skip Phase 3 on trivial diffs (e.g. typo) and say so
  • End with Verdict: Approve | Approve with nits | Request changes | Block — one-sentence justification

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

adhd

無料

Formats output for ADHD-friendly action — lead with the next step, number tasks, restate state, cut fluff. Use when named (adhd), when the user mentions ADHD or focus/executive-function constraints, or when they ask for steps they can execute immediately.

日本語の概要は準備中です。原文の説明を表示しています。

nateslabach/skills62026年9月29日 更新

Devil's-advocate attack on AI workflow designs — threat model, assumption challenges, code critiques, and hypothetical redesigns with no file edits. Use for "attack this design", devil's advocate, or hostile challenge on agents/tools/summarization/tokens. Not for PR peer review (code-review) or self-review that applies fixes (ai-systems-review). Prefer: this skill → decide → ai-systems-review.

日本語の概要は準備中です。原文の説明を表示しています。

nateslabach/skills62026年9月29日 更新

Hostile self-review of recently written AI workflow code that then applies fixes (agents, tools, chat context, summarization, tokens, attachments). Use after generating AI systems code, or when asked to self-review and harden it. Not for PR peer review (code-review) or no-edit devil's-advocate attacks (adversarial-challenge). Prefer: adversarial-challenge → decide → this skill.

日本語の概要は準備中です。原文の説明を表示しています。

nateslabach/skills62026年9月29日 更新

Writes in ASD-STE100 simplified technical English — short sentences, plain words, active voice. Use when the user wants terse technical prose, names this skill, or asks for STE100.

日本語の概要は準備中です。原文の説明を表示しています。

nateslabach/skills62026年9月29日 更新

branding

無料

Builds personal brand assets using Seth Godin's frameworks: signature symbol, slogan, surprise (Purple Cow), salient idea, and signature story. Use when named (branding), or when the user asks for a brand symbol, slogan, tagline, Purple Cow, counterintuitive angle, core idea, brand story, or personal brand positioning.

日本語の概要は準備中です。原文の説明を表示しています。

nateslabach/skills62026年9月29日 更新

Disables the AI's default hedging, diplomatic softening, and social-nicety layers to deliver cold, unfiltered, consequentialist analysis on any topic. Use when the user wants the AI's actual assessment without padding, regardless of how harsh or uncomfortable the honest answer is.

日本語の概要は準備中です。原文の説明を表示しています。

nateslabach/skills62026年9月29日 更新

nateslabach のスキルをすべて見る

このスキルの問題を報告する