Generate .pre-commit-config.yaml with security scanning, linting, and formatting hooks
Generates optimized .pre-commit-config.yaml files with security, linting, and formatting hooks for Python projects.
npx claudepluginhub jugrajsingh/skillgardenThis skill is limited to using the following tools:
references/pre-commit-base.yamlCreate optimized .pre-commit-config.yaml for Python projects.
Ruff replaces: black, autopep8, autoflake, isort, flake8, flake8-bandit
Still needed:
Dropped:
Glob: .pre-commit-config.yaml
If exists, ask via AskUserQuestion:
If existing config contains black, isort, flake8, autopep8, autoflake, or bandit, ask:
question: "Detected tools that ruff replaces. Migrate to ruff?"
header: "Migration"
options:
- label: "Yes, replace with ruff"
description: "Remove black/isort/flake8/bandit, use ruff instead"
- label: "No, keep existing"
description: "Keep current setup unchanged"
Tools ruff replaces:
Read the base config from references/pre-commit-base.yaml and use it as the starting template.
Customizations to apply based on project context:
chart/ directory, remove the exclude: '^chart/templates/' from check-yamlCopy the base config to .pre-commit-config.yaml with applicable sections uncommented.
Created .pre-commit-config.yaml
Hooks installed:
Security: gitleaks, pip-audit, detect-private-key
Validation: check-ast, check-yaml/json/toml, debug-statements
Git hygiene: no-commit-to-branch, check-merge-conflict
Formatting: ruff (lint+fix), ruff-format, whitespace fixes
Ruff replaces: black, isort, flake8, bandit, autopep8
Install: pre-commit install
Run all: pre-commit run --all-files
Update: pre-commit autoupdate
Ruff's S rules (flake8-bandit) cover the same security checks:
Enable in pyproject.toml:
[tool.ruff.lint]
select = ["S"] # Security rules
Check latest versions:
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.