code-review

Automate structural code quality analysis for web and JavaScript projects.

Updated May 3, 2024
One-click install
npx skills add https://github.com/Kyonax/dot-files --skill code-review-kyonax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Kyonax/dot-files/tree/main/.config/doom-mac/gptel-directives/skills/code-review
Command: npx skills add https://github.com/Kyonax/dot-files --skill code-review-kyonax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, node, gh, python3, and includes scripts (resource) components.

What problem does it solve?

This skill eliminates inconsistent and time-consuming manual code reviews by providing automated, structured quality analysis for web and JavaScript projects. It catches accessibility violations, SEO issues, code style problems, and framework-specific anti-patterns before they reach production, saving teams hours of review time and preventing costly bugs.

Core Features & Use Cases

  • Three-Tier Rule Selection: Automatically loads brand, project, and tech-stack specific rules based on git remote, file paths, and package.json, ensuring every review is relevant and noise-free.
  • Parallel AI Workers: Distributes analysis across specialized workers for ADA accessibility, SEO, Vue 3 patterns, Express conventions, and brand-specific disciplines like Kyonax FPS optimization.
  • 153 Atomic Rules: One rule per file covering ADA, code style, script patterns, mobile viewport, third-party SDK integration, SEO metadata, and project-specific conventions.
  • Use Case: A team preparing a PR for a Vue 3 e-commerce feature can run a full review that catches heading hierarchy errors, missing canonical tags, unused variables, and performance anti-patterns in a single pass.

Quick Start

Use the code-review skill to analyze the changed files in your current pull request and report any accessibility, SEO, or code style violations.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review for Vue 3 and Express pull requests?

You can automate code review for Vue 3 and Express pull requests by running parallel AI workers that fetch PR files via GitHub CLI and apply 153 atomic rules. The system catches accessibility violations, SEO issues, and framework-specific anti-patterns in a single pass.

How does automated accessibility audit for JavaScript codebases work?

Automated accessibility audits for JavaScript codebases work by distributing analysis across specialized parallel AI workers that detect ADA violations, heading hierarchy errors, and mobile viewport issues. The system applies one rule per file to check structural code quality before production deployment.

Do I need GitHub CLI and Node.js to run automated pre-merge quality gates?

Yes, automated pre-merge quality gates require GitHub CLI for PR fetching, Node.js for script execution, git for brand detection, and Python3. These dependencies coordinate parallel AI workers and shell-based preprocessing pipelines to analyze changed files in your pull request.

Can I load brand-specific and project-specific rules for SEO metadata checks?

Yes, you can load brand-specific and project-specific rules for SEO metadata checks using a three-tier rule selection system. The system automatically loads rules based on git remote, file paths, and package.json to ensure every review is relevant and noise-free for your specific project conventions.

What's the best way to catch SEO issues and code style violations before production?

The best way to catch SEO issues and code style violations before production is using a three-tier detection system with 153 atomic rules. Parallel AI workers analyze ADA accessibility, SEO metadata, script patterns, and framework-specific anti-patterns to prevent costly bugs in a single automated pass.

Why does automated code review load different rules for different git remotes?

Automated code review loads different rules for different git remotes to apply brand, project, and tech-stack specific conventions. This three-tier rule selection ensures every review is relevant and noise-free by matching rules to git remote, file paths, and package.json configurations.