Automated summary
Detects a project's linter configuration, runs lint and formatting checks, and categorizes issues by severity with their locations.
Strengths
- Auto-detects linters for Python (ruff, flake8, pylint), JavaScript (eslint), Go (golangci-lint) and YAML (yamllint)
- Structured report with a severity summary table, clean/issues status, and per-file issue details
- Respects project configuration and surfaces misconfiguration errors rather than failing silently
- Reports how many issues are auto-fixable with the --fix flag
Limitations
- Read-only by default: no automatic fixes are applied without an explicit request
- Covers only the linters named in the spec, with no extension to other ecosystems
- Does not describe how missing or uninstalled linters are handled
Use it when you want a quick, readable snapshot of code quality for a project or a set of files.
Do not use it to apply automatic fixes or to run type checks and tests, which are outside its scope.
Security analysis
SafeThe skill only runs standard, read-only linting and formatting checks using well-known tools and explicitly forbids auto-fixes unless requested. No destructive commands, credential access, network exfiltration, obfuscation, or safety-disabling behavior is present.
No concerns found
How this analysis is madeExamples
Run the lint checks on the src/ directory and summarize the issues by severity.Lint app/utils.py and tell me which problems are auto-fixable.Detect the project's linter configuration and lint the whole repository, then report findings per file.name: aget-lint-code description: Run code linting and formatting checks archetype: developer allowed-tools:
- Bash
- Read
- Glob
aget-lint-code
Run code linting and formatting checks on files or directories. Auto-detects linter configuration and reports issues by severity.
Instructions
When this skill is invoked:
-
Detect Linter Configuration
- Python: ruff, flake8, pylint (pyproject.toml, setup.cfg)
- JavaScript: eslint (.eslintrc.*)
- Go: golangci-lint (.golangci.yml)
- YAML: yamllint
-
Execute Linter
- Use project configuration
- Target specified files or all
- Capture output
-
Process Results
- Categorize by severity (error, warning, info)
- Extract file locations
- Count issues
-
Report Findings
- Summary by severity
- Issue details with locations
- Fix suggestions if available
Execution Commands
# Python (ruff)
ruff check [path] --output-format=text
# Python (flake8)
flake8 [path]
# JavaScript (eslint)
npx eslint [path] --format stylish
# Go
golangci-lint run [path]
# YAML
yamllint [path]
Output Format
## Lint Results
### Summary
| Severity | Count |
|----------|-------|
| Errors | [N] |
| Warnings | [N] |
| Info | [N] |
| **Total** | [N] |
### Status: [CLEAN/ISSUES FOUND]
### Issues by File
#### [filename.py]
| Line | Severity | Rule | Message |
|------|----------|------|---------|
| [N] | Error | [E001] | [Description] |
| [N] | Warning | [W002] | [Description] |
### Auto-fixable
[N] issues can be auto-fixed with `--fix` flag.
### Recommended Actions
1. [Fix critical errors first]
2. [Address warnings]
Constraints
- C1: NEVER apply auto-fixes without explicit --fix flag — lint is read-only by default
- C2: NEVER ignore configuration files — project configuration must be respected
- C3: NEVER fail silently when linter is misconfigured — configuration errors must be surfaced
Related
- SKILL-023: aget-lint-code specification
- ONTOLOGY_developer.yaml: Code, Code_Change concepts
- CAP-DEV-002: Code Linting capability
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/code-linting-and-formatting-mrwakcvz/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/code-linting-and-formatting-mrwakcvz' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-linting-and-formatting-mrwakcvz/download' --output '.skill-downloads/code-linting-and-formatting-mrwakcvz/SKILL.md.part' && mv '.skill-downloads/code-linting-and-formatting-mrwakcvz/SKILL.md.part' '.skill-downloads/code-linting-and-formatting-mrwakcvz/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/code-linting-and-formatting-mrwakcvz/SKILL.md' && test -s '.skill-downloads/code-linting-and-formatting-mrwakcvz/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/aget-lint-code' && cp -R '.skill-downloads/code-linting-and-formatting-mrwakcvz' '.claude/skills/aget-lint-code'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/code-linting-and-formatting-mrwakcvz'openskills read 'code-linting-and-formatting-mrwakcvz'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/code-linting-and-formatting-mrwakcvz/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.