Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Code Review

Checked
dauquangthanh·vlatest·frontend·MIT

Helps with frontend development, code review as part of building frontend UIs and user experiences workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add dauquangthanh/hanoi-rainbow --skill frontend-code-review -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

dauquangthanh

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned dauquangthanh/hanoi-rainbow at 0e2ebaea02.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0e2ebaea02
Manifest
skills/frontend-code-review/SKILL.md
Scanned
6 files, 4,878 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides automated frontend code review capabilities. It analyzes provided code snippets, identifies potential issues related to style, best practices, and common errors, and suggests improvements for enhanced code quality. The reviews are designed to be actionable and help developers write cleaner, more maintainable frontend code.

When to use it

  • Reviewing pull requests before merging into the main branch.
  • Getting feedback on newly written components or features.
  • Ensuring consistency across a codebase by enforcing style guidelines.
  • Identifying potential bugs or performance bottlenecks in existing frontend code.

Key capabilities

  • Automated code analysis
  • Style guide enforcement
  • Error detection
  • Suggestion of improvements

Example prompts

  • "Review this React component for potential issues: [code snippet]"
  • "Can you check this Vue.js file against the standard coding conventions?"
  • "Analyze this JavaScript code and suggest ways to improve its readability."

Tips & gotchas

The skill's effectiveness depends on the clarity and completeness of the provided code snippets. For best results, provide full files or components rather than isolated lines of code.