opensource-contributions
/opensource-contributions
Make good open source contributions — check CONTRIBUTING.md first, follow project norms, be a good citizen. Covers bug reports, feature requests, and pull requests with a defensible default posture when the project hasn't documented expectations. Do not use this skill for unrelated requests; route to the nearest named specialist.
- Author
- magnus919 ↗
- Repository
- agent-skills ↗
- Licence
- MIT
- Last repository change
- 25.10.2026
Assessment and security
- Files in this package
- 28
- Scripts
- 1
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
- 1 scripts in this package. Review them before installing, as Claude may execute them.
Scripts: scripts/check-pr-template-compliance.py
What it does and when to use it
Make good open source contributions — check CONTRIBUTING.md first, follow project norms, be a good citizen. Covers bug reports, feature requests, and pull requests with a defensible default posture when the project hasn't documented expectations. Do not use this skill for unrelated requests; route to the nearest named specialist.
Original author description
Make good open source contributions — check CONTRIBUTING.md first, follow project norms, be a good citizen. Covers bug reports, feature requests, and pull requests with a defensible default posture when the project hasn't documented expectations. Do not use this skill for unrelated requests; route to the nearest named specialist.
How it works
- The Golden Rule
- When to Use This Skill
- Quick Phase Overview
- The Agent-Specific Rule
- Quick Reference Card
- When NOT to Use This Skill
SKILL.md preview
---
name: opensource-contributions
description: >-
Make good open source contributions — check CONTRIBUTING.md first, follow project norms,
be a good citizen. Covers bug reports, feature requests, and pull requests with a
defensible default posture when the project hasn't documented expectations. Do not use
this skill for unrelated requests; route to the nearest named specialist.
license: MIT
compatibility: Compatible with any agent supporting the Agent Skills format (Hermes
Agent, Claude Code, GitHub Copilot, OpenCode, Cursor, etc.)
metadata:
tags: opensource, contributing, github, etiquette, PRs, issues
related_skills: github-issues, github-pr-workflow, github-code-review
version: 1.6.0
author: agent-skills
source_repo: https://agentskills.io
---
# Open Source Contributions
## The Golden Rule
**Make it easy for maintainers to absorb your contribution.** Maintainers are often under-resourced volunteers or small teams. Every friction point you remove — unclear reproduction steps, missing tests, bad commit messages, force-pushed history — is time they don't have to spend figuring out what you did and why. The whole point is to *help* them, not create more work.
## When to Use This Skill
- Filing a bug report or feature request on a public repository
- Preparing a pull request for any open source project
- Working on a project without documented contributing guidelines (default posture)
- Reviewing your own PR before submission
- Setting up open source conventions for your own project
**Load the relevant phase reference for detailed instructions.**
---
## Quick Phase Overview
| Phase | What It Covers | Reference |
|-------|----------------|-----------|
| **0a — Maintainer Conventions** | README discipline, LICENSE, CONTRIBUTING.md, issue/PR templates, commit conventions, DCO, release workflow hygiene | `references/phase-0a-maintainer-conventions.md` |
| **0 — Before You Start** | Reading CONTRIBUTING.md, checking existing issues/PRs, triaging bugfix candidates, large-change discussion etiquette | `references/phase-0-before-you-start.md` |
| **1 — Filing Issues** | Bug report and feature request templates, agent disclosure, maintainer workflow ("issue first"), coordinated multi-issue roadmaps, multi-PR plan execution | `references/phase-1-filing-issues.md` |
| **2 — Pull Requests** | Branching conventions, scope assessment, studying existing implementations, cross-repo comparison, commit messages, PR templates, documentation audits, CI setup | `references/phase-2-pull-requests.md` |
| **3 — After Submitting** | CI monitoring, responding to review feedback, what to do if your PR goes stale or gets closed | `references/phase-3-after-submitting.md` |
| **3.5 — Follow-up After Scope Feedback** | Systematic call-site audits, filing comprehensive issues, complementary PRs when maintainer scope notes identify gaps | `references/phase-35-followup.md` |
| **4 — Release Process** | Version bumping, tagging, GitHub Releases vs tags, release workflow anatomy, handling failed releases | `references/phase-4-release-process.md` |
### Default Posture (No CONTRIBUTING.md)
When a project has no contributing guide, load `references/default-posture.md` for defensible defaults on issue filing, PRs, communication norms, and code of conduct.
### Agent-Specific Checklist
If you are an AI agent filing or contributing on behalf of a human, load `references/agent-checklist.md` before submitting anything.
### Pitfalls
Load `references/pitfalls.md` when you're about to submit an issue or PR, or when something goes wrong. Covers: backtick expansion, silent label failures, force-push etiquette, the "I'll just fix it quickly" trap, cross-fork PR issues, post-merge scope creep, the installed-code trap, CI debugging, and more.
---
## The Agent-Specific Rule
When filing an issue on behalf of a human, **always disclose the agentic nature.** Add this line at the bottom of the issue body:
```
Filed by {{AGENT_NAME}} (AI agent on behalf of {{HUMAN_NAME}})
```
This is a transparency requirement, not a courtesy. Maintainers deserve to know who they're talking to.
---
## Quick Reference Card
| Step | Action | Command / Check |
|------|--------|-----------------|
| 0 | Read contributing guide | `cat CONTRIBUTING.md` or `.github/CONTRIBUTING.md` |
| 0 | Check existing issues | `gh issue list --search "topic" --state all` |
| 1 | File a bug/feature | Use template if provided; include reproduction for bugs |
| 2 | Issue first before coding | File issue, wait for maintainer feedback, then branch |
| 3 | Branch | `git checkout -b fix/description` |
| 4 | Commit | `git commit -s -m "fix: description"` |
| 5 | Run tests locally | `make test` or `npm test` or `pytest` |
| 6 | Push | `git push -u origin HEAD` |
| 7 | Open PR | Fill out PR template completely. Use `--body-file` for complex bodies |
| 8 | Monitor CI | `gh pr checks --watch` |
| 9 | Address review | Respond to comments, push fixup commits. No force-push after review |
| 10 | After merge | `git checkout main && git pull && git tag vX.Y.Z && git push origin main --tags` |
| 11 | Create Release | `gh release create vX.Y.Z --title "vX.Y.Z — Title" --notes-file /tmp/notes.md` |
---
## When NOT to Use This Skill
- You're the sole maintainer of a project with no external contributors and no public collaborators
- You're making a trivial single-line fix to your own code
- The contribution is internal (same organization, same team) with established workflow norms
- You already know the project's contributing guidelines by heart and this is routine
- The issue is a security vulnerability — follow the project's security disclosure policy instead
Files in this package (28)
- README.md 1 KB
- SKILL.md 6 KB
- evals/evals.json 3 KB
- references/agent-checklist.md 2 KB
- references/ci-debugging-loop.md 9 KB
- references/contribution-idea-filtering.md 5 KB
- references/cross-fork-org-restriction.md 3 KB
- references/cross-fork-pr-workaround.md 3 KB
- references/default-posture.md 2 KB
- references/gh-pr-create-body-pitfall.md 1 KB
- references/groktocrawl-gaps-worked-example.md 4 KB
- references/hermes-agent-contributing-case-study.md 3 KB
- references/hermes-cashew-contributing-worked-example.md 4 KB
- references/phase-0-before-you-start.md 12 KB
- references/phase-0a-maintainer-conventions.md 11 KB
- references/phase-1-filing-issues.md 14 KB
- references/phase-2-pull-requests.md 17 KB
- references/phase-3-after-submitting.md 1 KB
- references/phase-35-followup.md 6 KB
- references/phase-4-release-process.md 4 KB
- references/pitfalls.md 18 KB
- references/rebase-conflict-resolution.md 4 KB
- references/release-workflow-completion.md 5 KB
- references/remote-code-exploration.md 3 KB
- references/sequential-pr-conflict-resolution.md 3 KB
- references/sleep-cycle-refactor-worked-example.md 5 KB
- references/tracking-upstream-fix-status.md 4 KB
- scripts/check-pr-template-compliance.py 3 KB
Versions
The database has no other skills named opensource-contributions.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 697a52e1dd65 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100open-source-contributions
Create maintainer-friendly pull requests with clean code and professional communication. Prevents 16 common mistakes that cause PR rejection. Use when: contributing to open source, submitting PRs, or troubleshooting PR rejection, CI failures, or personal artifacts in commits. - 100document-project
Generate comprehensive, professional project documentation structures including README, ARCHITECTURE, USER_GUIDE, DEVELOPER_GUIDE, and CONTRIBUTING files. Use when the user requests project documentation creation, asks to "document a project", needs standard documentation files,… - 100autonom-gh-contribute
Prepare and verify responsible contributions to third-party GitHub repositories, including reproductions, documentation, tests and pull requests. Use when investigating or contributing upstream, checking repository policies, or following up on an existing contribution. - 100opensource
Start an open-source agent-skill package, TypeScript single package or workspace, or common-only repository with consistent public files and guarded release setup. Use for new projects, not to replace an existing project's architecture. - 100opensource-pipeline
Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'. Use when a private project must be forked,… - 100opensource-pipeline
Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'. Use when a private project must be forked,…