code-review

Reviews pull request diffs against repository-specific lint, security, and versioning rules.

54|6|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/schmitthub/clawker --skill code-review-schmitthub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/schmitthub/clawker/tree/main/.github/skills/code-review
Command: npx skills add https://github.com/schmitthub/clawker --skill code-review-schmitthub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests consistently against a repository's custom rules is time-consuming and error-prone. This Skill automates a structured review of pull requests, diffs, or branches in the clawker repository, checking each change against the project's defined priority rules. ## Core Features & Use Cases - Lint Suppression Detection: Scans every added or changed line for //nolint, #nosec, and //lint:ignore suppressions and reports each as a priority 1 comment. - Control Plane Security Checks: Verifies gRPC servers and listeners use the correct auth interceptor chain, lane-specific certificates, mutual TLS settings, and panic-safe serve goroutines. - Repository Convention Enforcement: Validates CLAUDE.md symlinks point to AGENTS.md and confirms all version pins (Docker FROM, GitHub Actions uses:, image constants) carry SHA digests or full commit SHAs. - Use Case: When a teammate opens a pull request adding a new gRPC listener under controlplane/, invoke this Skill to automatically verify the auth interceptor, certificate lane isolation, and version pinning before approving. ## Quick Start Ask the AI to review the current pull request or branch diff using the code-review procedure defined for this repository.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request with this Skill?▼

Invoke the Skill when asked to review a pull request, diff, or branch. It follows a six-step procedure covering lint suppressions, control plane listeners, CLAUDE.md files, version pins, standing rules, and a final prioritized report.

What checks does this code review perform on gRPC servers?▼

It confirms the gRPC server attaches the controlplane/auth interceptor in the correct chain order, uses certificates from the listener's own lane, enforces RequireAndVerifyClientCert with CN or SAN pinning when applicable, and avoids panic, log.Fatal, or os.Exit without recover.

Does this Skill work for repositories other than clawker?▼

The procedure is tailored to the clawker repository, referencing paths like controlplane/, cmd/clawkercp/, and .github/copilot-instructions.md. Applying it elsewhere would require adapting those repository-specific rules and paths.

How are version pins validated in a pull request?▼

Each added FROM line, uses: line, rev: line, or Go image constant must carry a @sha256: digest or a full commit SHA. Any missing pin is reported as a priority 4 finding.

What is the CLAUDE.md symlink rule?▼

Each CLAUDE.md in the diff must have file mode 120000 (a symlink) with content exactly AGENTS.md, and an AGENTS.md file must exist in the same directory. Git submodules are exempt from this check.