code-review
No SKILL.md available for this skill.
View on GitHubMore from helderberto/skills
a11y-audit
Audit accessibility compliance in frontend code. Use when user asks to "check accessibility", "/a11y-audit", "audit a11y", "check WCAG", or wants to find accessibility issues. Don't use for backend code, non-UI files, or projects without HTML/JSX output.
17prose-fix
Fix prose formatting, typos, and clarity issues in markdown or text files. Use when user asks to "fix dashes", "fix typos", "clean up text", "improve sentences", or "/prose-fix". Don't use for code style, linting, or full rewrites.
16revise
Structurally edit and improve article drafts — reorder sections, tighten arguments, improve clarity. Use when user asks to "revise", "improve my article", "edit my draft", or "/revise". Don't use for typo fixes or formatting (use prose-fix), code documentation, or non-article content.
16checks
Pre-commit quality gate: auto-fix formatting/lint, verify types, run tests. Use when user asks to \"run checks\", \"/checks\", \"verify before commit\", or wants to validate code quality. Don't use for committing, pushing, or writing new tests.
7source-driven
Implement features using official docs for exact dependency versions instead of training data. Use when user asks to "check the docs", "use official docs", "source-driven", or when implementing with unfamiliar APIs/libraries. Don't use for well-known stdlib APIs or project-internal code.
5precommit
Pre-commit quality gate: auto-fix formatting/lint, verify types, run tests. Use when user asks to \"run precommit\", \"/precommit\", \"verify before commit\", or wants to validate code quality. Don't use for committing, pushing, or writing new tests.
3