SkillsAdd

nvidia/elements · Archived

audit-code

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 assess code quality. Trigger on phrases like "review these changes," "check this code," "give feedback," "look at the staged files," "review this PR," or "before comm…

First seen Aug 17, 2026

Installation

$ npx skills add nvidia/elements --skill audit-code
View on skills.sh ↗ GitHub repository ↗

Summary

  • 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 assess code quality.
  • Trigger on phrases like "review these changes," "check this code," "give feedback," "look at the staged files," "review this PR," or "before committing.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

api-design Same source
nvidia/elements

Component API design patterns following Elements conventions for properties, attributes, CSS cu…

2 installs
troubleshooting Same source
nvidia/elements

Diagnose and resolve common issues including test failures, build errors, performance regressio…

2 installs
authoring-typescript Same source
nvidia/elements

Best practices for TypeScript code including type safety, discriminated unions, type guards, an…

2 installs
guidance-build Same source
nvidia/elements

Wireit orchestration, build optimization, caching strategies, and build troubleshooting for the…

1 installs

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

agent-browser Shared topics
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
azure-diagnostics Shared topics
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs
azure-validate Shared topics
microsoft/azure-skills

Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure…

567.7K installs
azure-rbac Shared topics
microsoft/azure-skills 489K installs
supabase-postgres-best-practices Shared topics
supabase/agent-skills

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …

391.6K installs
building-native-ui Shared topics
expo/skills 59.2K installs

Also in this package

Other skills from nvidia/elements · top by installs.

npx skills add nvidia/elements
api-design 2 troubleshooting 2 authoring-typescript 2 guidance-build 1 audit-accessibility 1 availability-report 1 github-dependabot 1 component-creation 1 testing 1 authoring-documentation 1

Browse all from nvidia/elements

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 85
License LICENSE
Default branch main
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,953 B
  • docs SUMMARY.md 524 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Audit Code

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 behavior 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 each changed file type (not all guidelines):

  • .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.