Skip to content
TrustedSkillsbeta
Back to all skills

Lint And Validate

Checked
davila7·vlatest·backend·MIT

Analyzes and validates frontend code against best practices, style guides, and potential errors using davila7's custom linting rules.

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 davila7/claude-code-templates --skill lint-and-validate -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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Commit
79182c51fb
Manifest
cli-tool/components/skills/development/lint-and-validate/SKILL.md
Scanned
3 files, 393 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

The lint-and-validate skill automates code quality checks for frontend projects, ensuring syntax correctness and adherence to style guides before deployment. It integrates directly with your development workflow to catch errors early and maintain consistent coding standards across the team.

When to use it

  • Before pushing code to a shared repository or staging environment.
  • When integrating new team members who need to follow specific style conventions.
  • During pull request reviews to automatically flag formatting issues.
  • When refactoring legacy codebases to modernize syntax and structure.

Key capabilities

  • Runs automated linters on JavaScript, TypeScript, and JSX files.
  • Validates code against configurable ESLint rulesets.
  • Provides detailed error reports with file locations and line numbers.
  • Supports both inline feedback and batch validation modes.

Example prompts

"Run a full lint check on the src/components directory and list all errors." "Validate my new React component against our team's strict ESLint configuration." "Fix any syntax errors found in the build output and show me the corrected code."

Tips & gotchas

Ensure your project has an .eslintrc file configured before running validation to avoid generic rule failures. For large monorepos, consider splitting checks by package to reduce execution time and improve feedback granularity.