Quality Run Linting Formatting
CheckedAutomates code quality checks, linting, and formatting to ensure consistent style and identify potential issues.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add dawiddutoit/custom-claude --skill quality-run-linting-formatting -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
dawiddutoit
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.
Automated safety checks
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 dawiddutoit/custom-claude at 17b45a90a6.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 17b45a90a6
- Scanned
- 1 file, 528 lines
About this skill
What it does
This skill automatically runs linting and formatting on code files. It ensures consistent style, identifies potential errors through static analysis, and applies automated fixes to improve code quality. The process helps maintain a clean codebase and reduces manual effort in code review.
When to use it
- Automated Code Review: Integrate into your workflow to automatically check for style violations and potential issues before merging changes.
- Consistent Formatting: Enforce a uniform coding style across a project or team, improving readability and collaboration.
- Quick Fixes: Automatically apply formatting and linting fixes to large codebases, saving time and effort.
- Pre-Commit Hooks: Run the skill as part of a pre-commit hook to prevent poorly formatted or flagged code from being committed.
Key capabilities
- Runs linters (e.g., ESLint, PyLint)
- Applies formatting rules (e.g., Prettier, Black)
- Automated fixes for linting errors and style violations
- Supports multiple programming languages
Example prompts
- "Run linting and formatting on this Python file:
my_script.py." - "Apply Prettier to all JavaScript files in the current directory."
- "Check this code for style violations and suggest fixes: [paste code here]"
Tips & gotchas
- The skill's effectiveness depends on having appropriate linting and formatting configurations set up for your project. Ensure you have configured linters and formatters (e.g.,
.eslintrc.js,pyproject.toml) beforehand.