Collaboration
- 13 installs
- 82 repo stars
- Updated August 2, 2026
- aaaaqwq/claude-code-skills
collaboration is a Claude Code skill that documents how to collaborate on GitHub projects through forks, branches, PRs, code reviews, and issues.
About
collaboration is a Claude Code skill documenting how to collaborate on GitHub projects. It covers working with write versus read-only access, creating forks and branches, opening PRs toward main, doing inline code reviews, addressing review comments, and managing issues on the original repository. A developer uses it when contributing to projects, creating PRs, or reviewing code on GitHub.
- Guide for collaborating on GitHub projects: forks, branches, PRs, reviews, and issues
- Covers write vs read-only access, fork-based workflow, and inline PR review conventions
- Documents addressing review comments and post-merge branch syncing
Collaboration by the numbers
- 13 all-time installs (skills.sh)
- Ranked #410 of 735 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 3, 2026 (Skillselion catalog sync)
collaboration capabilities & compatibility
- Capabilities
- github collaboration · pull requests · code review · fork workflow
- Works with
- github
- Use cases
- code review · project management
What collaboration says it does
Create a new branch (never commit directly to main)
Always create GitHub issues on the original repository, never on the fork.
npx skills add https://github.com/aaaaqwq/claude-code-skills --skill collaborationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 13 |
|---|---|
| repo stars | ★ 82 |
| Last updated | August 2, 2026 |
| Repository | aaaaqwq/claude-code-skills ↗ |
What it does
Follow GitHub collaboration conventions for forks, branches, PRs, code reviews, and issues.
Who is it for?
Contributing to GitHub projects via forks, branches, and PRs and doing inline code reviews
Skip if: Non-GitHub version control workflows
When should I use this skill?
Contributing to projects, creating PRs, reviewing code, or managing issues on GitHub
By the numbers
- Documents the full fork-branch-PR-review-merge collaboration cycle
Files
Collaboration
This skill documents how to collaborate on projects on GitHub.
Working on Projects
With write access
If you have write access to the project, you may work directly in the project.
With read-only access
If you only have read-only access and cannot write directly to any branches:
1. Create a fork under your own GitHub user account 2. Work exclusively on the fork, not the original repository 3. The fork is your workspace for all development
Making Changes
To submit changes to a project:
1. Create a new branch (never commit directly to main) 2. Make commits on this branch as work progresses 3. When ready, create a PR from the working branch towards the main branch (from one repo to another if it's a fork)
Code Reviews
When asked to review code:
1. Do the review directly on the GitHub PR 2. Add comments inline in the code where they make sense 3. Use general PR comments only for overarching feedback
Addressing Review Comments
When responding to review feedback:
1. Address comments on GitHub, not just in code 2. Reply to each comment explaining what was changed or why something was kept 3. Mark conversations as resolved when the feedback has been addressed
After PR is Merged
Once a PR has been merged:
1. Switch back to the main branch 2. Pull from origin to sync with the merged changes
Issues
Always create GitHub issues on the original repository, never on the fork. The fork is only for development work, if needed.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148