**Version**: 2.0.0 | **Last Verified**: 2025-11-18 | **Production Tested**: ✅
/plugin marketplace add secondsky/claude-skills/plugin install open-source-contributions@claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/error-catalog.mdreferences/pr-templates.mdreferences/workflow-guide.mdtemplates/pr-description.mdtemplates/pre-submission-checklist.mdtemplates/validate-pr.shVersion: 2.0.0 | Last Verified: 2025-11-18 | Production Tested: ✅
cat CONTRIBUTING.md # ALWAYS read first
cat CODE_OF_CONDUCT.md
# Fork on GitHub, then:
git clone https://github.com/YOUR-USERNAME/project.git
cd project
git remote add upstream https://github.com/ORIGINAL-OWNER/project.git
# NEVER work on main!
git checkout -b feature/add-oauth-support
# Make changes
npm test
npm run build
npm run lint
# Commit
git commit -m "feat(auth): add OAuth2 support"
# Run validation script
bash scripts/validate-pr.sh # Load from templates/validate-pr.sh
# Push
git push origin feature/add-oauth-support
Use template from templates/pr-description.md - include What/Why/How/Testing/Evidence
Load references/workflow-guide.md for complete step-by-step workflow.
NEVER commit directly to main/master branch
# ❌ WRONG: Working on main
git checkout main
git commit -m "add feature" # DON'T DO THIS
# ✅ CORRECT: Create feature branch
git checkout -b feature/my-feature
git commit -m "add feature" # This is correct
Why?
Recovery if you committed to main:
# Move commits to feature branch
git branch feature/my-feature # Create branch with commits
git reset --hard upstream/main # Reset main to upstream
git checkout feature/my-feature # Switch to feature branch
NEVER submit untested code
Required testing:
Required evidence in PR description:
## Testing
### Automated Tests
- [x] All existing tests pass (450/450)
- [x] Added 15 new tests for feature
- [x] Coverage: 92%
### Manual Testing
- [x] Tested on Chrome, Firefox, Safari
- [x] Tested edge cases and error states
- [x] Performance testing (handles 1000+ items)
### Evidence
- Screenshot: [feature working](link)
- Video: [full walkthrough](link)
Why?
One PR = One Feature
# ❌ WRONG: Multiple unrelated changes
git checkout -b feature/oauth-and-bugfixes
# Adding OAuth + fixing 5 unrelated bugs
# ✅ CORRECT: Separate branches for separate concerns
git checkout -b feature/add-oauth # Just OAuth
git checkout -b fix/pagination-bug # Just pagination fix
git checkout -b fix/login-redirect # Just login fix
Good PRs:
Bad PRs:
Why?
Load references/error-catalog.md for all 16 mistakes and detailed fixes.
For complete catalog: Load references/error-catalog.md when making any contribution to see all 16 mistakes, detailed fixes, and prevention strategies.
Quick list (most common):
Prevention: Run templates/validate-pr.sh before every PR to catch these automatically.
For detailed fixes and code examples: Load references/error-catalog.md
For complete workflows: Load references/workflow-guide.md when implementing any contribution pattern.
Quick trigger guide:
fix/ branch, test, commit with "Fixes #123"feature/ branch, implement incrementallydocs/ branch, edit, commit with "Closes #789"templates/validate-pr.sh (automated) or templates/pre-submission-checklist.md (manual)For step-by-step commands and patterns: Load references/workflow-guide.md → specific workflow section
references/workflow-guide.md when:references/error-catalog.md when:references/pr-templates.md when:Personal Development Artifacts (NEVER include):
❌ SESSION.md, NOTES.md, TODO.md # Session notes
❌ planning/*, research-logs/* # Planning docs
❌ screenshots/debug-*, screenshots/test-* # Debug screenshots
❌ test-manual.js, quick-test.py # Temp test files
❌ IMPLEMENTATION_PHASES.md # Project planning
❌ SCRATCH.md, DEBUGGING.md # Temporary notes
Use validation script to check:
bash scripts/validate-pr.sh # Load from templates/
Load references/error-catalog.md → Mistake #2 for complete list.
For complete checklist: Load templates/pre-submission-checklist.md when validating PR before submission.
Quick essentials:
Automated validation: Run templates/validate-pr.sh to check automatically.
For complete command reference: Load references/workflow-guide.md when setting up fork, syncing with upstream, or managing contribution workflow.
Essential commands:
git clone → git remote add upstreamgit pull upstream main → git push origin maingit checkout -b feature/name → test → commit → bash scripts/validate-pr.shgit push origin feature/name → create PR on GitHubgit branch -d feature/nameLoad references/workflow-guide.md → "Quick Command Reference" for detailed commands.
For complete templates: Load references/pr-templates.md when writing PR descriptions or communicating with maintainers.
Key principles:
Common scenarios: Claiming issues, receiving feedback, following up on PRs - all covered in references with example templates.
For complete solutions: Load references/workflow-guide.md → "Troubleshooting" when encountering git issues or PR problems.
Common problems:
All solutions with commands available in workflow-guide.md
The 3 Critical Rules (detailed in lines 79-185):
Before Every PR: Run validate-pr.sh script, remove artifacts, test thoroughly
Load references/error-catalog.md to avoid all 16 common mistakes.
References (references/):
error-catalog.md - All 16 common mistakes that annoy maintainers with prevention strategiespr-templates.md - PR description templates and writing best practicesworkflow-guide.md - Complete contribution workflow (includes commit message best practices, PR sizing guidelines)Templates (templates/):
validate-pr.sh - Pre-PR validation scriptQuestions? Issues?
references/error-catalog.md for all 16 mistakesreferences/workflow-guide.md for complete workflowreferences/pr-templates.md for PR descriptionstemplates/validate-pr.sh before every PRCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.