maintainer-community-fileslisted
Install: claude install-skill vivekbhange-hub/maintainer-skill
# Community files
Generic templates get ignored because they describe some other project. These files work when
they contain this repo's real commands, real folder names, and real people. This skill reads
the repo first and writes only what is missing (or improves what is thin), so a newcomer can go
from clone to passing tests by following CONTRIBUTING.md word for word.
## Steps
1. **Inventory what exists.** Check the root, `.github/`, and `docs/` for: CONTRIBUTING, SECURITY,
CODE_OF_CONDUCT, SUPPORT, `.github/ISSUE_TEMPLATE/`, `pull_request_template.md`, CODEOWNERS,
FUNDING.yml. If `maintainer-health` ran, reuse its report. Never overwrite an existing file
without asking; offer a diff with proposed additions instead.
2. **Extract the real facts.** Read, do not assume:
- Language and tooling: `package.json` (scripts, packageManager, engines), `pyproject.toml`
(build backend, tool sections), `Cargo.toml`, `go.mod`, `Makefile`, `justfile`, `tox.ini`, `noxfile.py`.
- Install, test, lint, format, and build commands, preferring what CI runs
(`.github/workflows/*.yml` steps). If README and CI disagree, trust CI and note the drift.
- Supported runtime versions (CI matrix, `engines`, `requires-python`, `rust-version`).
- Commit style: `git log -n 50 --pretty=%s` (conventional commits or not).
- Default branch: `gh repo view --json defaultBranchRef,hasDiscussionsEnabled,securityPolicyUrl,isPrivate`.
- Maintainers: top committers per directory,