Skip to content
TrustedSkillsbeta
Back to all skills

Lint Fix Parallel

Checked
te19oishi·vlatest·backend

This skill swiftly identifies and fixes code style issues (linters) in multiple files simultaneously, boosting developer productivity.

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 te19oishi/my-skills --skill lint-fix-parallel -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

te19oishi

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 te19oishi/my-skills at 8edb296e06.

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

Commit
8edb296e06
Manifest
.claude/skills/lint-fix-parallel/SKILL.md
Scanned
2 files, 182 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-fix-parallel skill automatically identifies and corrects code style issues within a codebase. It leverages parallel processing to significantly speed up the linting and fixing process, making it suitable for large projects. This skill ensures consistent coding standards across teams and reduces manual effort in maintaining clean code.

When to use it

  • Large Codebases: Ideal for projects with many files where traditional linting can be slow.
  • Enforcing Coding Standards: Automate the process of adhering to specific style guides (e.g., PEP 8 for Python).
  • Pre-Commit Hooks: Integrate into a development workflow to automatically fix code before committing changes.
  • Continuous Integration/Continuous Delivery (CI/CD): Ensure code quality and consistency as part of automated build pipelines.

Key capabilities

  • Parallel linting and fixing
  • Automated code style correction
  • Support for various programming languages (specific languages not listed)
  • Integration with existing development workflows

Example prompts

  • "Fix all linting errors in the src directory."
  • "Run a parallel linter on my Python project and apply fixes."
  • "Correct code style according to PEP 8 for the entire repository."

Tips & gotchas

The skill requires appropriate linting configuration files (e.g., .eslintrc.js, pyproject.toml) to be present in the codebase. Ensure these configurations are set up correctly before using the skill, as it relies on them to identify and fix issues.