Skip to content
cleder

cleder/gpc-init

CLILive in production

Generate a pre-commit or prek .pre-commit-config.yaml for your project from curated language and framework presets — so you get the right linters, formatters, a

Initialize a prek/pre-commit yaml with recommended checks

8 4 since joining 3PythonPush 23h agoListed 2mo ago4 open issuesGPL-3.0
pre-commitpre-commit-hooks
  • Python62.3%
  • Shell27.2%
  • JavaScript6.7%
  • PowerShell3.8%
View on GitHub

Report a problem

1 Review

pc-init turns a repetitive setup task into a well-designed command-line workflow. Its language and framework catalog is data-driven, with metadata and preset files kept beside each other instead of hard-coded throughout the application. The CLI supports explicit selection, repository detection, aliases, framework recommendations, profiles, custom local or Git-based catalogs, safe diff output, and force-controlled replacement. The bundled coverage is extensive, spanning many languages and frameworks along with common hooks. Documentation explains detection rules, preset composition, version pinning, custom catalogs, and the contribution quality bar in concrete terms.
The repository also has a strong verification story. Large unit and integration suites exercise catalog loading, detection, resolution, merging, rendering, remote fetching, and CLI behavior. CI tests Python 3.13 through 3.15 development builds, runs three strict type checkers, multiple complexity tools, formatting checks, package inspection, coverage reporting, preset validation, and trusted PyPI publication. The main improvements involve release clarity and accessibility. The source declares version 0.9.0, while the changelog and current published package stop at 0.8.0, so unreleased status should be clearly marked or documented. Requiring Python 3.13 significantly limits adoption for a general developer utility and deserves either broader compatibility or a clear explanation of the dependency. The very long README would also benefit from moving catalog tables and advanced maintenance details into separate documentation pages. Finally, because generated configurations execute third-party hooks and custom catalogs can come from Git repositories, a short trust and security section should explain revision pinning, catalog review, and the risks of running unfamiliar hooks.