Skip to main content
Developer Documentation / Project Tools

CONTRIBUTING.md Generator

Generate a CONTRIBUTING.md guide with setup steps, test commands, branch and commit conventions, and a pull request checklist.

Describe how to set up, test and submit changes to your project, and get a contributor guide GitHub links to from every new issue and pull request.

Commands you enter are copied into the guide as text - nothing is run.

What Is the CONTRIBUTING.md Generator?

It creates a CONTRIBUTING.md guide that explains how to set up your project, make a change, write commit messages and open a pull request. GitHub links to this file when someone opens an issue or pull request, so it is the first thing new contributors see.

When to Use It

  • Opening a project to outside contributors for the first time.
  • Onboarding new team members to an internal repository.
  • Answering the same "how do I run the tests?" question for the tenth time.

How to Use It

  1. Enter the project name and repository URL.
  2. List the setup commands and the test and lint commands, one per line.
  3. Choose the main branch, the commit message style and which requirements to include.
  4. Click Generate CONTRIBUTING.md and save the file in the repository root or .github/.

Example

With the setup commands npm install and cp .env.example .env and the test command npm test, the guide includes a numbered setup section with those commands in code blocks and a pull request checklist that asks contributors to run npm test first.

Understanding the Output

The guide has a table of contents, bug and feature reporting guidance, development setup, a "making a change" section, commit message rules (Conventional Commits or plain descriptive messages) and a pull request checklist. Commands you enter are copied as text - they are never run.

Limitations

The generator cannot know your project's architecture or review rules, so add anything specific to your team afterwards. Pair it with a CODEOWNERS file for automatic reviewers, a SECURITY.md for vulnerability reports, and conventional commit messages from the Git Commit Message Generator.

Frequently Asked Questions

In the repository root, the docs folder or the .github folder. GitHub then shows a link to it when someone opens a new issue or pull request.

A commit message format such as "fix(auth): handle expired tokens", with a type like feat, fix or docs and an optional scope. It makes history easy to scan and lets tools generate changelogs and version bumps automatically.

No. The commands are only copied into the Markdown as text in code blocks. Nothing is executed, stored or sent anywhere.

Yes, even a short one helps. Explaining how to run the project and the tests saves contributors time and saves you from reviewing pull requests that were never tested.
Share this tool: