What problem does it solve? New or partially configured repositories often lack CI pipelines, README files, CODEOWNERS, SECURITY.md, and other hygiene files, and manually adding them risks overwriting existing maintainer customizations. ## Core Features & Use Cases - Idempotent repo bootstrapping: Copies a full template set (.gitignore, .editorconfig, .env.example, GitHub Actions CI/CodeQL workflows, Dependabot config, CODEOWNERS, issue/PR templates, README, CONTRIBUTING, SECURITY.md, CHANGELOG.md, library/ docs schema) without ever clobbering existing files. - Placeholder resolution: Fills template tokens from observable repo context such as package.json, git remote, lockfiles, and existing LICENSE files. - Verification reporting: Produces a three-part report covering files already present, files created, and items needing human decisions like branch protection, secret scanning, and license choice. - Use Case: Point it at a freshly created Node/TypeScript repository and receive a working CI pipeline, community health files, and a documentation library, plus a checklist of GitHub Settings actions only an admin can complete. ## Quick Start Ask the assistant to initialize this repository to a healthy baseline with CI, README, and community health files using the get-started-stinger skill.
