Skip to content
Skills Library
Programming · Review & audit

audit-code

/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 committing.

Repository
elements ↗
Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

Triggers from the description

review these changes,check this code,give feedback,look at the staged files,review this PR,
Original author description

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.

How it works

  1. When to Use This Skill
  2. Change Context
  3. Guideline Context
  4. Files to Review
  5. Output Format
Original SKILL.md headings · 71 lines, 318 words
SKILL.md preview
---
name: audit-code
description: 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."
---

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

Versions

RepositoryScoreLicence
This page · nvidia/elements100Apache-2.0
Come-In-Labs/agent-skills100MIT
paulnewmandev/pn-ultra-audit100GPL-3.0
yowcow/dude86MIT
aAAaqwq/AGI-Super-Team85MIT

Database snapshot: 13.11.2026 · package version 985cf04aefd0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100code-review
    This skill should be used when the user asks for a code review of a change — a pull request, merge request, branch, commit range, working-tree change, or pasted diff — covering correctness, security, performance, structure, and repository-specific rules. Trigger on phrases like…
  • 96skill-staged-review
    Use when a PR or feature needs both specification and code-quality review
  • 100code-review
    Use to review code changes with a two-stage process - first checking spec/requirements compliance, then code quality. Works on staged changes, branches, or PRs.
  • 100review-guidelines
    Review code changes for compliance with CLAUDE.md guidelines. Use when the user says 'review guidelines', 'check guidelines', or 'validate against guidelines'.
  • 100review-code
    Perform a senior-engineer code review when the user asks to review code, review a PR, review changes, or check code quality
  • 100pre-commit-review
    Review staged and unstaged changes before committing. Use when asked for a pre-commit review, a code-quality review of the current diff, or when a solve workflow requests an independent review.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.