Skip to content
TrustedSkillsbeta
Back to all skills

Lint Format

Checked
1mangesh1·vlatest·utilities

Automatically formats code according to specified style guides, ensuring consistency and readability across projects.

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 1mangesh1/dev-skills-collection --skill lint-format -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

1mangesh1

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 1mangesh1/dev-skills-collection at 23e297e5a4.

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

Commit
23e297e5a4
Manifest
skills/lint-format/SKILL.md
Scanned
7 files, 664 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

The lint-format skill ensures code adheres to defined style guides and formatting rules. It automatically checks for stylistic errors and inconsistencies, then reformats the code to match the specified standards. This promotes clean, readable, and maintainable codebase across projects.

When to use it

  • Enforcing Code Style: When a team wants to ensure all contributions adhere to a specific coding style (e.g., PEP 8 for Python).
  • Automated Formatting: To automatically format code during development or as part of a CI/CD pipeline, reducing manual effort.
  • Preparing Code for Review: Before submitting code for review, use this skill to ensure it's consistently formatted and free from style-related issues.
  • Standardizing Legacy Code: To gradually bring older codebases into compliance with modern coding standards.

Key capabilities

  • Code linting
  • Automatic code formatting
  • Style guide enforcement

Example prompts

  • "Lint and format this Python file according to PEP 8."
  • "Run the formatter on all JavaScript files in this directory."
  • "Check if this code adheres to our team's style guidelines."

Tips & gotchas

The skill requires a configured linter/formatter (e.g., flake8, black, ESLint) and associated configuration files for proper operation. Ensure these are set up correctly before using the skill; otherwise, it may produce unexpected results or fail to execute.