agentleFS
maragudkmaragudk/skills/collaboration/SKILL.md

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
  1. Distinctive:

    If you have write access to the project, you may work directly in the project.

    line 15
  2. Distinctive:

    If you only have read-only access and cannot write directly to any branches:

    line 19
  3. Distinctive:

    Create a fork under your own GitHub user account

    line 21
  4. Distinctive:

    Create a new branch (never commit directly to main)

    line 29
  5. Distinctive:

    When ready, create a PR from the working branch towards the main branch (from one repo to another if it's a fork)

    line 31
  6. Distinctive:

    When asked to review code:

    line 35
  7. Distinctive:

    Do the review directly on the GitHub PR

    line 37
  8. Distinctive:

    Add comments inline in the code where they make sense

    line 38
  9. Distinctive:

    Use general PR comments only for overarching feedback

    line 39
  10. Distinctive:

    When responding to review feedback:

    line 43
  11. Distinctive:

    Always create GitHub issues on the original repository, never on the fork.

    line 58

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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.