run-code-quality-tool
Automates linting and formatting for specific project directories using Pylint and Ruff.
Install
mkdir -p .claude/skills/run-code-quality-tool && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10636" && unzip -o skill.zip -d .claude/skills/run-code-quality-tool && rm skill.zipInstalls to .claude/skills/run-code-quality-tool
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when source code changes under lib/jnpr/junos and the user wants to run static code analysis and code format using pylint and ruffKey capabilities
- →Run static code analysis
- →Format Python code
- →Detect changed source files
- →Execute pylint and ruff checks
How it works
The skill detects changed Python files under a specific directory, runs ruff formatting checks, and executes pylint analysis, reporting results for each.
Inputs & outputs
When to use run-code-quality-tool
- →Formatting changed files
- →Running lint checks
- →Cleaning up Python code
- →Ensuring code quality in junos
About this skill
Run Code Quality Tool
Goal
Run formatting checks and static analysis for Python changes under lib/jnpr/junos.
Required Workflow
1) Install required code-quality tools
Install pylint and ruff before running checks:
python3 -m pip install pylint ruff
2) Detect changed Python source files
Collect changed files under lib/jnpr/junos and keep only .py files.
Preferred commands:
git diff --name-only -- lib/jnpr/junos | grep -E '\\.py$'git diff --name-only --cached -- lib/jnpr/junos | grep -E '\\.py$'
3) Run ruff format check for diff files
Run formatting check for only changed Python files under lib/jnpr/junos:
CHANGED=$( (git diff --name-only -- lib/jnpr/junos; git diff --name-only --cached -- lib/jnpr/junos) | grep -E '\\.py$' | sort -u )if [ -n "$CHANGED" ]; then echo "$CHANGED" | xargs -I{} ruff format --check "{}"; else echo "No changed Python files under lib/jnpr/junos"; fi
4) Run pylint for changed files under lib/jnpr/junos
Run pylint for only changed Python files first:
CHANGED=$( (git diff --name-only -- lib/jnpr/junos; git diff --name-only --cached -- lib/jnpr/junos) | grep -E '\\.py$' | sort -u )if [ -n "$CHANGED" ]; then pylint $CHANGED --exit-zero; else echo "No changed Python files under lib/jnpr/junos"; fi
5) Optional full ruff format for all Python files
If requested, run ruff format across all tracked Python files:
git ls-files '*.py' | xargs -I{} ruff format "{}"
6) Optional full pylint command
If requested, run the broader pylint command:
pylint $(git ls-files '*.py' | grep -vE '^(docs/|build/|tests/|samples/|setup.py|versioneer.py)') --exit-zero
Output Contract
When this skill is invoked, the final response must include:
- Changed Python files detected under
lib/jnpr/junos. ruff format --checkresult for changed files.pylintresult for changed files.- If optional full ruff format was run, include that result separately.
- If full pylint was run, include that result separately.
When not to use it
- →Non-Python codebases
- →Full project-wide cleanup without request
Prerequisites
Limitations
- →Limited to lib/jnpr/junos directory
- →Requires manual installation of tools
How it compares
It focuses on incremental quality checks for specific directories, ensuring only changed code is validated unless a full run is requested.
Compared to similar skills
run-code-quality-tool side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| run-code-quality-tool (this skill) | 0 | 3mo | No flags | Beginner |
| adk-engineer | 3 | 27d | Review | Advanced |
| unit-testing-test-generate | 2 | 4mo | Review | Intermediate |
| playwright-roll | 2 | 2mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Juniper
View all by Juniper →You might also like
adk-engineer
jeremylongshore
Execute software engineer specializing in creating production-ready ADK agents with best practices, code structure, testing, and deployment automation. Use when asked to "build ADK agent", "create agent code", or "engineer ADK application". Trigger with relevant phrases based on skill purpose.
unit-testing-test-generate
sickn33
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
playwright-roll
microsoft
Roll Playwright Python to a new version
api-test-generator
mikopbx
Генерация полных Python pytest тестов для REST API эндпоинтов с валидацией схемы. Использовать при создании тестов для новых эндпоинтов, добавлении покрытия для CRUD операций или валидации соответствия API с OpenAPI схемами.
designing-tests
CloudAI-X
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-coverage-improver
openai
Improve test coverage in the OpenAI Agents Python repository: run `make coverage`, inspect coverage artifacts, identify low-coverage files, propose high-impact tests, and confirm with the user before writing tests.