contributing

Standardizes contribution guidance for software projects via a YAML-frontmatter Markdown template.

1|2|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/alunduil/alunduil-chezmoi --skill contributing-alunduil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: contributing
Source: https://github.com/alunduil/alunduil-chezmoi/tree/main/dot_claude/skills/contributing
Command: npx skills add https://github.com/alunduil/alunduil-chezmoi --skill contributing-alunduil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes contribution guidance for software projects.

Core Features & Use Cases

  • Template-driven guidance for issues, PRs, and documentation.
  • Onboarding & consistency across repositories with a reusable workflow.
  • Quick adoption by teams needing minimal setup.

Quick Start

Apply the nayafia/contributing-template to create or update a project's CONTRIBUTING.md.

Frequently Asked Questions about contributing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create contributing guidelines for an open-source project?

To create contributing guidelines, you can apply a template-driven approach to standardize guidance for issues, pull requests, and documentation. This ensures onboarding consistency across repositories with minimal setup for external contributors.

What should be included in a CONTRIBUTING.md file for pull requests and code review?

A CONTRIBUTING.md file should include template-driven guidance for pull requests, code review procedures, and documentation standards. It standardizes contribution guidance to help open-source teams maintain consistency when accepting external submissions.

How do I standardize contribution workflows across multiple repositories?

You can standardize contribution workflows across multiple repositories by applying a reusable template. This provides template-driven guidance for issues, PRs, and documentation, ensuring onboarding and consistency with minimal setup for each project.

Does this approach work for personal configurations as well as open-source teams?

Yes, this contribution guidance approach applies to both open-source teams and personal configurations. It covers issues, PRs, reviews, and documentation to guide external contributors regardless of project scale or team size.

What is the best way to onboard external contributors to a software project?

The best way to onboard external contributors is to provide clear, actionable contribution guidelines using a standardized template. This covers issues, PRs, reviews, and documentation, guiding new contributors through the expected workflow.

Why do I need a structured template for contribution guidelines?

You need a structured template for contribution guidelines to solve the problem of standardizing contribution guidance for software projects. It ensures quick adoption by teams needing minimal setup while maintaining consistency across repositories.