| name | collaboration |
| description | Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub. |
| license | MIT |
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:
- Create a fork under your own GitHub user account
- Work exclusively on the fork, not the original repository
- The fork is your workspace for all development
Making Changes
To submit changes to a project:
- Create a new branch (never commit directly to main)
- Make commits on this branch as work progresses
- 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:
- Do the review directly on the GitHub PR
- Add comments inline in the code where they make sense
- Use general PR comments only for overarching feedback
Addressing Review Comments
When responding to review feedback:
- Address comments on GitHub, not just in code
- Reply to each comment explaining what was changed or why something was kept
- Mark conversations as resolved when the feedback has been addressed
After PR is Merged
Once a PR has been merged:
- Switch back to the main branch
- 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.
