Code Linting

Name: Code Linting
Author: aspiers

Checked

aspiers·vlatest·backend·GPL-3.0

Code Linting analyzes your code for potential errors and style issues, improving code quality and reducing bugs.

Repository

Install on your platform

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

Run this in your project

terminal

$ npx skills add aspiers/ai-config --skill code-linting -a claude-code

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

aspiers

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 1 Oct 2026

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 aspiers/ai-config at 6c29f2480e.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 6c29f2480e
Manifest: .agents/skills/code-linting/SKILL.md
Scanned: 1 file, 40 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 code linting, identifying potential errors and style inconsistencies in your codebase. It helps maintain code quality by enforcing coding standards and best practices. The skill can be used to improve readability and reduce bugs through consistent formatting and error detection.

When to use it

Before submitting a pull request: Ensure all changes adhere to project coding guidelines.
During code reviews: Quickly identify potential issues for discussion.
As part of CI/CD pipelines: Automatically check code quality on every commit.
For onboarding new developers: Enforce consistent style across the team.

Key capabilities

Automated code analysis
Enforcement of coding standards
Identification of potential errors
Style consistency checks

Example prompts

"Lint this Python file: [file path]"
"Check this JavaScript code for errors and style issues."
"Run the linter on all files in my project directory."

Tips & gotchas

This skill requires a configured linter (e.g., ESLint, PyLint) to be effective. Ensure your project has appropriate linting rules defined before using this skill.