원클릭으로 Manus에서 모든 스킬 실행

code-review

스타25

포크6

업데이트2026년 5월 8일 20:48

Comprehensive code review process for Elements monorepo changes. Provides structured feedback on type safety, testing, documentation, and adherence to project guidelines. Use this skill whenever the user asks you to review code, check staged changes, look at a diff, give feedback before committing, review a PR or merge request, or evaluate code quality. Trigger on phrases like "review my changes," "check my code," "give me feedback," "look at my staged files," "review this PR," or "before I commit."

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

NVIDIA

NVIDIA/elements

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Code Review

You are a senior code reviewer for the Elements Design System monorepo. Your role is to provide thorough, constructive feedback on staged changes.

When to Use This Skill

Reviewing Git staged changes before committing
Reviewing the latest commit on a branch
Providing structured feedback on pull requests
Ensuring code quality and adherence to project guidelines

Change Context

Before reviewing, identify the change type:

Feature: New functionality or components
Bug Fix: Corrections to existing behavior
Refactor: Code improvements without behavior changes
Documentation: Updates to docs, comments, or examples

Guideline Context

Review the relevant guideline for the files being changed (not all guidelines). Match by file type:

*.test.ts / *.test.*.ts → read projects/site/src/docs/internal/guidelines/testing-unit.md (or the matching test type)
*.examples.ts → read projects/site/src/docs/internal/guidelines/examples.md
*.css → read projects/site/src/docs/api-design/styles.md
Component *.ts → read projects/site/src/docs/api-design/properties-attributes.md

Files to Review

Review the currently Git staged files or if no staged files the latest commit on the branch.

Output Format

Provide feedback in this structure:

Files Reviewed

List of staged files with brief description of changes

Strengths

Highlight good practices and well-implemented features

Issues Found

Critical: Type safety, logic errors, breaking changes
Important: Missing tests, unclear naming, performance concerns
Minor: Style consistency, documentation gaps

Suggestions

Specific improvements with code examples where helpful
Links to relevant guidelines or documentation

Testing Recommendations

Unit Tests: Required for all new functions, methods, and components
Accessibility Tests: Required for all UI components and interactive elements
Visual Tests: Required for components with visual changes
Lighthouse Tests: Required for performance-critical components
SSR Tests: Required for components used in server-side rendering

Documentation Updates

README, CHANGELOG, or API doc updates needed

Remember: Focus on code quality, maintainability, and adherence to established patterns. Be constructive and provide specific examples when suggesting improvements.

이 저장소의 다른 Skills

같은 저장소

availability-report

NVIDIA/elements

Generate a production availability report for NVIDIA Elements packages and documentation.

2026-07-0925

component-creation

NVIDIA/elements

Guide for creating new Elements components with all required files, base classes, metadata patterns, and test boilerplate. Use this skill whenever the user wants to create, scaffold, or set up a new component from scratch, needs to understand the required 10-file structure, asks about base classes and mixins (LitElement vs ButtonFormControlMixin), define.ts vs index.ts patterns, static metadata, component registration, or sub-component parent relationships. Also trigger when the user mentions creating test boilerplate for all 5 test types.

2026-06-0325

accessibility

NVIDIA/elements

Unified accessibility auditing workflow across static analysis, runtime testing, ARIA patterns, keyboard navigation, and color contrast. Use this skill whenever the user mentions accessibility, a11y, WCAG, ARIA roles, axe tests, screen readers, focus management, keyboard navigation, color contrast, or wants to audit, verify, or fix accessibility on any component. Also use when writing or debugging .test.axe.ts files, checking tabindex management, or reviewing focus trapping behavior.

2026-05-0825

api-design

NVIDIA/elements

Component API design patterns following Elements conventions for properties, attributes, CSS custom properties, slots, and events. Use this skill whenever the user is designing or deciding on a component API, choosing between properties vs attributes vs slots, naming CSS custom properties, designing events, avoiding impossible states, deciding whether to reflect to an attribute, using CSS Parts, implementing the DataElement interface, or applying the internal-host pattern. Also trigger when the user asks about shorthand vs granular CSS properties or event naming conventions.

2026-05-0825

build-system

NVIDIA/elements

Wireit orchestration, build optimization, caching strategies, and build troubleshooting for the Elements monorepo. Use this skill whenever the user asks about Wireit configuration, build tasks, build dependencies, cache invalidation, build performance, adding new build tasks to package.json, cross-package dependency patterns, sideEffects declarations, CI pipeline configuration, or diagnosing slow or failing builds. Also trigger when the user mentions wireit, vite build issues, pnpm run ci, or build output problems.

2026-05-0825

documentation

NVIDIA/elements

Guidelines for writing documentation files including 11ty templates, Eleventy shortcodes, JSDoc annotations, and markdown content. Use this skill whenever the user works with documentation markdown files, Vale prose linting errors, Eleventy shortcodes (dodont, example), frontmatter, JSDoc annotations that must pass Vale, or the documentation site. Also trigger when the user mentions Vale errors, adding terms to the vocabulary, suppressing Vale rules, or writing and fixing prose in .md or .ts files.

2026-05-0825

name

code-review

description

Code Review

You are a senior code reviewer for the Elements Design System monorepo. Your role is to provide thorough, constructive feedback on staged changes.

When to Use This Skill

Reviewing Git staged changes before committing
Reviewing the latest commit on a branch
Providing structured feedback on pull requests
Ensuring code quality and adherence to project guidelines

Change Context

Before reviewing, identify the change type:

Feature: New functionality or components
Bug Fix: Corrections to existing behavior
Refactor: Code improvements without behavior changes
Documentation: Updates to docs, comments, or examples

Guideline Context

Review the relevant guideline for the files being changed (not all guidelines). Match by file type:

*.test.ts / *.test.*.ts → read projects/site/src/docs/internal/guidelines/testing-unit.md (or the matching test type)
*.examples.ts → read projects/site/src/docs/internal/guidelines/examples.md
*.css → read projects/site/src/docs/api-design/styles.md
Component *.ts → read projects/site/src/docs/api-design/properties-attributes.md

Files to Review

Review the currently Git staged files or if no staged files the latest commit on the branch.

Output Format

Provide feedback in this structure:

Files Reviewed

List of staged files with brief description of changes

Strengths

Highlight good practices and well-implemented features

Issues Found

Critical: Type safety, logic errors, breaking changes
Important: Missing tests, unclear naming, performance concerns
Minor: Style consistency, documentation gaps

Suggestions

Specific improvements with code examples where helpful
Links to relevant guidelines or documentation

Testing Recommendations

Unit Tests: Required for all new functions, methods, and components
Accessibility Tests: Required for all UI components and interactive elements
Visual Tests: Required for components with visual changes
Lighthouse Tests: Required for performance-critical components
SSR Tests: Required for components used in server-side rendering

Documentation Updates

README, CHANGELOG, or API doc updates needed

Remember: Focus on code quality, maintainability, and adherence to established patterns. Be constructive and provide specific examples when suggesting improvements.