Make Repo Contribution

Make Repo Contribution

make-repo-contribution skill for programming & development

Category: development Source: github

A guide to making quality open source contributions, covering the complete workflow from forking and branching to pull request creation, code review, and merge.

What Is This?

Overview

This skill provides a structured contribution workflow including repository forking, branch management, commit conventions, pull request best practices, and code review processes. It follows industry-standard patterns used by major open source projects.

Who Should Use This

Perfect for first-time open source contributors, experienced engineers joining new projects, maintainers writing contribution guides, and teams standardizing internal contribution workflows.

Why Use It?

Problems It Solves

Contributions often fail due to inconsistent commit messages, poorly structured pull requests, and misunderstanding project conventions. Contributors waste time on rejected PRs that don't follow established patterns, while maintainers spend time explaining basic workflow steps repeatedly.

Core Highlights

  • Complete Workflow - Fork, branch, code, commit, push, PR, review, merge
  • Conventional Commits - Standardized commit message format
  • PR Best Practices - Templates, descriptions, and review readiness
  • Branch Strategy - Clean feature branches with proper naming
  • Review Readiness - Checklist for submission-ready contributions

How to Use It?

Basic Usage

Ask Claude about contributing to a repository, and this skill will guide the process.

Scenario 1: First Contribution Setup

Ask Claude: "Help me contribute to a GitHub project"

Claude will walk through the complete setup:

gh repo fork owner/project --clone
cd project

git checkout -b feat/add-search-filter

git add src/components/SearchFilter.tsx
git commit -m "feat(search): add filter component for results page

Implements dropdown filter with category selection.
Closes #142"

git push -u origin feat/add-search-filter
gh pr create --title "feat(search): add filter component"   --body "## Summary
- Adds SearchFilter component with category dropdown
- Integrates with existing search results page
- Includes unit tests for filter logic

Closes #142"

Scenario 2: Keeping Fork Updated

Tell Claude: "My fork is behind the upstream repository"

Claude will show:

git remote add upstream https://github.com/owner/project.git

git fetch upstream
git checkout main
git merge upstream/main
git push origin main

git checkout feat/add-search-filter
git rebase main

Real-World Examples

First Open Source PR

A junior developer contributed a documentation fix to a popular React library. Following conventional commit format and including a clear PR description, the contribution was merged within 24 hours.

Feature Contribution

An engineer added internationalization support to a CLI tool. By splitting the work into 3 focused PRs (config, translation loader, language switcher), each PR received fast reviews and merged within a week.

Advanced Tips

Commit Hygiene

Squash work-in-progress commits before submitting. Use git rebase -i to combine fixup commits into clean, logical commits that tell a clear story.

Pre-submission Checklist

Before creating a PR: run the full test suite, check linting, verify the build passes, read the diff entirely, and ensure your branch is rebased on the latest main.

When to Use It?

Use Cases

  • First Contribution - Set up fork, branch, and PR workflow correctly
  • Bug Fixes - Submit focused fixes with proper issue references
  • Feature Additions - Contribute new features following project conventions
  • Documentation - Improve docs, README, or code comments
  • Code Review - Respond to review feedback and update PRs

Related Topics

When you ask Claude these questions, this skill will activate:

  • "How do I contribute to an open source project?"
  • "Create a pull request for this repository"
  • "Set up fork and branch for contribution"
  • "Write conventional commit messages"

Important Notes

Requirements

  • Git 2.30+ with branching and rebasing knowledge
  • GitHub account with SSH keys configured
  • GitHub CLI (gh) recommended for efficient workflows
  • Understanding of the project's language and tooling
  • Read CONTRIBUTING.md before starting

Usage Recommendations

Do:

  • Read CONTRIBUTING.md first - Follow the project's established guidelines
  • Keep PRs focused - One feature or fix per pull request
  • Write descriptive commits - Use conventional commit format
  • Test thoroughly - Run the full test suite before submitting

Don't:

  • Don't submit large PRs - Break big changes into smaller chunks
  • Don't ignore CI failures - Fix all checks before requesting review
  • Don't force push after review - Add new commits for transparency

Limitations

  • Maintainers may have slow response times for reviews
  • Some projects require a Contributor License Agreement
  • CI pipelines differ between projects
  • Not all repositories accept external contributions