What problem does it solve? New or bare repositories often lack consistent formatting, automated checks, contributor conventions, and a release path, leading to style debates, broken commits, and unclear licensing. This Skill bootstraps that baseline quality scaffolding while detecting and matching the repo's existing stack instead of imposing new defaults. ## Core Features & Use Cases - Stack detection first: Inspects existing config (pyproject.toml, package.json, workflows) and matches the tools already in use rather than substituting preferred defaults like ruff over an existing black/isort/flake8 setup. - Hygiene checklist: Adds .editorconfig, formatter and linter config, pinned .pre-commit-config.yaml with a no-commit-to-branch hook, Makefile entrypoints, .gitattributes, LICENSE, README, and a CI workflow mirroring local checks. - Versioning and release path: Confirms license and versioning scheme with the operator, recommends SemVer with a 0.x phase for libraries, single-sources the version, and keeps a Keep-a-Changelog CHANGELOG.md. - Use Case: When asked to "set up proper repo hygiene" on a Python package that already has black and isort configured, the Skill wires pre-commit, Makefile targets, and CI around those existing tools in small, reviewable commits. ## Quick Start Ask the agent to use the repo-hygiene-init skill to set up repo hygiene, tooling, and automation for this repository.
