| name | code-review |
| description | OUDS Web compliance code review. Use this skill when reviewing a diff, preparing a commit, or when asked to check code quality. Acts as a safety net that verifies all OUDS conventions are respected: token usage (no hardcoded values, no raw tokens), required mixins (border-radius, transition), accessibility (ARIA, focus-visible), multi-brand sync (tokens in all 3 brands), and file hygiene (no dist/, no auto-gen edits). Invoke proactively before any commit or PR submission. |
Code Review (OUDS Compliance)
Purpose
This skill is a safety net. It catches OUDS convention violations that other skills might have missed. Invoke it before committing or when reviewing diffs.
Checklist
For each changed file in the diff, verify:
SCSS files (**/*.scss)
JavaScript files (js/src/**/*.js)
HTML/MDX files
Token/brand files (packages/**)
General
How to use
- Run
git diff --stat to see changed files
- For each file category, apply the relevant checklist section
- Report violations with file, line, and suggested fix
- Classify: ERROR (must fix) vs WARNING (should fix)
Report format
## Code Review: OUDS Compliance
### ❌ Errors (must fix before merge)
- `scss/_buttons.scss:42` — hardcoded `padding: 8px` → use `$ouds-space-*` token
- `js/src/tooltip.js:15` — semicolon present → remove
### ⚠️ Warnings (should fix)
- `scss/_card.scss:88` — missing `// OUDS mod:` on Bootstrap override
### ✅ Passed
- Token cross-brand check: all present
- No dist/ files in diff
- ARIA attributes correct