agentleFS
hsnice16hsnice16/agent-friendly-code/.claude/skills/code-review/SKILL.md

code-review

Skill2 starsChanged 14 days agoMITView on GitHub

Reviews code changes for repo-specific best practices — Tailwind usage, constants/utils extraction, I/O boundary, React Server Components, and component reuse. Triggers during PR review or after non-trivial edits to app/, components/, or lib/.

194 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use close-spec, design-with-images and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dzhngSkill

    close-spec

    When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).

    Also in 5 projects that use this

  • dzhngSkill

    design-with-images

    Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.

    Also in 5 projects that use this

  • PydanticSkill

    add-new-model

    Add support for a newly-released language or image generation model in pydantic-ai (e.g. openai:gpt-5.6, anthropic:claude-sonnet-5, openai:gpt-image-2). Use when a provider ships a new model id and you need to wire literals, profile flags, adapters, and tests to recognize it. Handles SDK-lag, gateway list conventions, capability probing, and direct image-model geometry.

    Also in 9 projects that use this

  • transitive-bullshitSkill

    compare-screenshots

    Compare screenshots against the intended design, distinguishing approved references from historical baselines. Use for iterative implementation matching, before/after visual review, objective image telemetry, or checking a lone capture for flat, empty, or badly framed content.

    Also in 5 projects that use this

  • Microsoft AzureSkill

    azsdk-common-apiview-feedback-resolution

    Analyze and resolve APIView review feedback on Azure SDK PRs. **UTILITY SKILL**. USE FOR: APIView comments, API review feedback, SDK API surface changes. DO NOT USE FOR: general code review, non-APIView feedback. INVOKES: azure-sdk-mcp:azsdk_apiview_get_comments, azure-sdk-mcp:azsdk_customized_code_update, azure-sdk-mcp:azsdk_typespec_delegate_apiview_feedback, azure-sdk-mcp:azsdk_run_typespec_validation, azure-sdk-mcp:azsdk_package_generate_code.

    Also in 6 projects that use this

  • Microsoft AzureSkill

    azsdk-common-generate-sdk-locally

    Generate and finalize Azure SDKs locally from TypeSpec, including build, checks, tests, changelog, metadata, and version updates by default. WHEN: "generate SDK locally", "build SDK", "run SDK tests", "run CI checks", "validate package", "run checks", "update changelog", "fix SDK build errors", "resolve SDK generation errors", "customize TypeSpec", "rename SDK client", "rename SDK model", "hide operation from SDK", "fix analyzer errors", "resolve customization drift", "create subclient", "update metadata", "update version". INVOKES: azsdk_verify_setup, azsdk_package_generate_code, azsdk_package_build_code, azsdk_package_run_check, azsdk_package_run_tests, azsdk_customized_code_update, azsdk_package_update_changelog_content, azsdk_package_update_metadata, azsdk_package_update_version.

    Also in 6 projects that use this

  • +4 more from dzhng
  • +2 more from Azure

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 184 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run through this checklist on any diff.

    line 8
  2. Very specific:

    Prefer utilities over custom classes: If a pattern can be expressed with existing Tailwind utilities, use them.

    line 12
  3. Very specific:

    Default to server components: Only add "use client" when you need state, effects, browser APIs, or event handlers.

    line 33
  4. Very specific:

    If you're writing the same markup 2–3 times, extract a component into components/.

    line 40
  5. Very specific:

    Only @phosphor-icons/react.

    line 46
  6. Distinctive:

    No color-only signals (pair color with text or icon).

    line 52
  7. Distinctive:

    Never execute code from a cloned repo.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 184 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Code review — repo best practices

Run through this checklist on any diff. Flag violations with the specific line and the suggested fix.

Tailwind

  • Prefer utilities over custom classes. If a pattern can be expressed with existing Tailwind utilities, use them. Don't add a custom class in app/globals.css unless the pattern repeats 3+ times with the same composition.
  • Use the @theme tokens (bg-surface, text-ink, border-line, etc.) — never hardcode hex in JSX.
  • No style={{ ... }} unless the value is dynamic (e.g. width: ${pct}%). Static styling belongs in className.
  • No @apply in globals.css (Tailwind 4 best practice — put the utilities on the element instead, or extract a React component).

Constants + utils

  • Magic numbers → lib/constants/ (e.g. SCORE_THRESHOLD_GOOD, LEADERBOARD_PAGE_SIZE).
  • Repeated formatting → lib/utils/format.ts (compactStars, relativeTime, hostLabel).
  • Repeated scoring logic → lib/utils/score.ts (scoreTier, TIER_TEXT_CLASS, TIER_BG_CLASS).
  • A helper that's used once doesn't belong in utils/; inline it.

I/O boundary (architecturally important)

  • lib/scoring/ stays pure — no DB imports, no HTTP, no side effects.
  • All SQL in lib/db*.ts. Don't call db.prepare(...) from pages or components.
  • Clients in lib/clients/ — git, host and registry APIs.
  • Pages and scripts are thin wrappers.

React Server Components

  • Default to server components. Only add "use client" when you need state, effects, browser APIs, or event handlers.
  • Fetch data in pages, pass props down. Components don't fetch.
  • Use <Link> from next/link for internal navigation, not <a href>.
  • Query params over client state where possible; the boards are the exception (AGENTS.md → Conventions).

Components

  • If you're writing the same markup 2–3 times, extract a component into components/.
  • Components are presentational — no data fetching, no side effects, except localStorage as AGENTS.md → Browser storage allows.
  • Props are typed explicitly; avoid any.

Icons

Only @phosphor-icons/react. Block Lucide, Heroicons, React Icons, inline SVG, emoji-as-icon. Import server components from @phosphor-icons/react/dist/ssr; client components from the root entry.

Accessibility (quick pass — delegate deeper checks to quality-check)

  • Icon-only affordances need aria-label.
  • Interactive elements are keyboard-reachable.
  • No color-only signals (pair color with text or icon).

Security

  • Parameterised SQL only.
  • dangerouslySetInnerHTML only in components/JsonLd.tsx (server-built JSON-LD, < escaped) and the constant pre-paint script in components/BoardPendingScript.tsx. Reject any other use.
  • External links include rel="noopener noreferrer".
  • Never execute code from a cloned repo.

Response format when reviewing

Group findings by severity:

  • Must fix: breaks conventions, security issues, accessibility blockers.
  • Should fix: best-practice violations, missing extractions.
  • Consider: minor polish.

Each finding cites the file + line and suggests the exact fix.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.