{"categories":[{"label":"Quality Assurance","url":"https://skillfed.io/packages/category/software-development-quality-assurance/3"}],"enrichment":{"capability":"Ick is a polyglot tool for bundling best practices as versioned, runnable rules and checking any number of repos against them\u2014with or without auto-fixes.","skillfed_tags":["multi-repo-automation","policy-as-code","compliance-scanning"],"use_cases":["A security team publishes a rule to scan GitHub Actions workflows with a tool like zizmor across all company repos without adding it to each repo individually.","An ML project enforces rules about approved model licenses or dependencies across multiple experiment repositories.","A developer maintains hobby-horse style rules (e.g., text files must end with a newline) and applies them consistently across personal projects.","A platform team checks that all repos have adopted a new Python version or removed a deprecated API, reporting which repos are compliant and which need work.","A project runs checks before release that verify documentation is up to date, changelog is populated, and version numbers are consistent."],"what_it_does":"Ick centralizes code quality and best-practice checks that would otherwise be scattered across pre-commit hooks, CI workflows, wiki pages, and one-off scripts. Instead of wiring the same checks into every repository individually, you write rules once in a central repository and run them against any target repo you need to audit. Rules can be simple checks (exit with a status code) or include auto-fixes; they can be written in any language and run in parallel by default.\n\nThe tool is designed for teams, projects, or individual developers who maintain multiple repositories and want to enforce consistent standards across them without per-repo configuration. It supports filtering rules by tags, reproducing results locally for debugging, and tracking compliance across many repos. When best practices evolve\u2014a new scanner ships, or a deprecated API needs removal\u2014you update the rule once rather than in every repository.","worth_installing":"Yes, if you maintain multiple repositories and want to enforce consistent checks without duplicating configuration in each one. The permissive MIT license, active maintenance, low install friction, and lack of known vulnerabilities make it safe to adopt. Best suited for teams or developers with strong opinions about code quality who want a single source of truth for rules. Not necessary if you only maintain one or two repos or rely entirely on pre-commit and CI for enforcement."},"id":"ick","links":{"html":"https://skillfed.io/packages/ick","md":"https://skillfed.io/packages/ick.md","pypi":"https://pypi.org/project/ick/"},"maintenance":{"status":"active"},"meta":{"latest_release":"2026-07-24","license_spdx":null,"license_treatment":"permissive","name":"ick","python_support":"supports_current","summary":"Applier of fine source code fixes since 2025"},"popularity":{"monthly_downloads":191891,"position":9873,"tier":"top_15000"},"security":{"n_vulnerabilities":0},"version":"0.12.0"}