skills.rest
blackplume233
blackplume233COMMUNITY
Explore all skills by this author →
GitHub

contribution-policy

Standardize contributor workflows with structured guidelines for issue triage, branch naming, and commits.

12|1|Updated Feb 19, 2026
Search Tags:#workflow#testing#docs#guidelines#code-review#contribute#open-source
One-click install
npx skills add https://github.com/blackplume233/Actant --skill contribution-policy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contribution-policy
Source: https://github.com/blackplume233/Actant/tree/main/examples/actant-hub/skills/contribution-policy
Command: npx skills add https://github.com/blackplume233/Actant --skill contribution-policy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide standardizes how contributors engage with the project by prescribing structured guidelines for issue selection, development planning, and quality assurance.

Core Features & Use Cases

  • Issue Selection Criteria: Prioritize labeled issues for onboarding; scope should be clear for effective contribution.
  • Branch Naming Convention: Use concise, lowercase, hyphen-separated names and include the Issue number when applicable.
  • Commit Message Convention: Follow conventional commits with a clear scope and rationale.
  • Testing & Documentation: Ensure tests exist and docs are updated to reflect changes.

Quick Start

Follow the CONTRIBUTING guidelines to submit a compliant pull request.

Frequently Asked Questions about contribution-policy

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

FAQPage Schema
How do I standardize open-source contributor workflows for issue triage and branch naming?▼

Standardize open-source contributor workflows by enforcing concise, lowercase, hyphen-separated branch names that include issue numbers for clear tracking across collaborative software projects.

What is the best commit message convention for collaborative software projects?▼

The best commit message convention for collaborative software projects follows conventional commits with a clear scope and rationale to ensure structured development planning and quality assurance.

How do I write contribution guidelines with YAML frontmatter and structured sections?▼

Write contribution guidelines by enforcing YAML frontmatter metadata, structured sections in the description, and a concise Quick Start to onboard new contributors effectively.

How do you triage labeled issues for onboarding new contributors?▼

Triage labeled issues for onboarding by prioritizing those with clear scope for effective contribution, ensuring new developers can select and scope tasks easily within open-source projects.

Do I need to update tests and docs when submitting a pull request?▼

Yes, you need to ensure tests exist and docs are updated to reflect changes before submitting a compliant pull request, maintaining project quality assurance and documentation standards.

Related Skills

Explore More Software Engineering Skills→
dmzoneilldmzoneill
2

start-work

Automate repository setup and branch management for Jira issues.

Community
Advanced
kk20300113-pngkk20300113-png

ship

Automate code release workflows from branch merging to pull request creation.

Community
Advanced
craigtkhillcraigtkhill

write-commit-message

Generate git commit messages following conventional commits syntax.

Community
Basic
thepradipthepradip

technical-writer

Generate Diataxis-structured developer documentation with templates and style guidelines.

Community
Advanced