collaboration
Skill49 starsChanged 9 months agoMITView on GitHub
Guide for collaborating on GitHub projects. This skill should be used when contributing to projects, creating PRs, reviewing code, or managing issues on GitHub.
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
If you have write access to the project, you may work directly in the project.
- Distinctive: line 19
If you only have read-only access and cannot write directly to any branches:
- Distinctive: line 21
Create a fork under your own GitHub user account
- Distinctive: line 29
Create a new branch (never commit directly to main)
- Distinctive: line 31
When ready, create a PR from the working branch towards the main branch (from one repo to another if it's a fork)
- Distinctive: line 35
When asked to review code:
- Distinctive: line 37
Do the review directly on the GitHub PR
- Distinctive: line 38
Add comments inline in the code where they make sense
- Distinctive: line 39
Use general PR comments only for overarching feedback
- Distinctive: line 43
When responding to review feedback:
- Distinctive: line 58
Always create GitHub issues on the original repository, never on the fork.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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:
- 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.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- vivy-yi/xiaohongshu-skills★ 455same name
- joaocarloscruz/skills★ 1same name
- Karatuss/bstack★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- address-code-reviewSkill
- autoresearchSkill
- blueskySkill
- brainstormSkill
- code-reviewSkill
- datastarSkill
- decisionsSkill
- design-docSkill
- diarySkill
- gardenSkill
- gitSkill
- gomponentsSkill
- goSkill
- marimoSkill
- nanobananaSkill
- observable-plotSkill
- save-web-pageSkill
- sqlSkill
- worktreesSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

