A complete, professional, and opinionated GitHub repository template designed to boost consistency, enhance collaboration, and support scalable open-source or private projects.
π¦ Ready-to-clone setup for teams who care about quality, clarity, and developer experience.
If you're tired of:
- inconsistent commit messages,
- undocumented contribution flow,
- messy collaboration practices,
- or setting up the same configs over and over again...
This repo is for you.
β Built to be reused β Just clone, customize, and start coding.
β
Optimized for collaboration β Complete with interactive commit flow via Commitizen and a powerful collaboration_guide.md.
β Zero Node.js dependency requirement β Works well even if your project isnβt JavaScript-based.
- π Predefined
.czrcfor consistent commit messages via Commitizen - π§ Clear Collaboration Guide
- π Semantic versioning & commit conventions (Conventional Commits)
- π οΈ GitHub-friendly structure with
.githubsupport - β‘ Clean and modular template to scale with your team
git clone https://github.com/your-username/init-repo-template.git your-project-name
cd your-project-name- Make sure you read the π
collaboration_guide.md. - It includes how to:
- Set up and use Commitizen with
.czrc - Follow the branching and PR workflow
- Keep documentation and changelogs clean
- Set up and use Commitizen with
git init
git remote add origin <your-new-repo-url>
npm install -g commitizen cz-git # or cz-conventional-changelog if preferredπ‘ Already includes
.czrcβ you're ready to usegit czright away.
.czrc is a configuration file for Commitizen. It defines how commit messages are written and which adapter to use.
We use it to:
- Maintain a clean Git history
- Enable automated changelog generation
- Improve team communication via clear commits
To commit using Commitizen:
git add .
git czAnd follow the interactive prompt.
Please always refer to collaboration_guide.md before pushing or opening a pull request. It explains:
- How we write commits
- How to open PRs
- Branch naming
- Code review etiquette
β Don't commit directly to
mainunless you're doing initial setup.
- Open-source project templates
- Internal company repositories
- Bootstrapping monorepos
- Teaching good Git practices to teams
init repo template, github repo starter, professional collaboration guide, conventional commit template, czrc guide without nodejs, interactive git commit convention, developer friendly repo structure, semantic commit bootstrap
Feel free to open an issue or start a discussion. This template evolves as more teams and individuals use it. Contributions are welcome!
MIT β use it freely, modify it proudly.
Want to see it in action? Clone this template into your own repo and make your first contribution using:
git czYou'll feel the difference in how structured and efficient your repo becomes π‘