agentleFS
ieeecsopenieeecsopen/mcp-cs/.agents/skills/campus-git-team-workflow/SKILL.md

campus-git-team-workflow

Skill3 starsChanged 3 months agoNo licenceView on GitHub

Activate when a student or team needs to set up, repair, or reason about a Git collaboration workflow for a university group project (semester project, hackathon team, final year project, capstone). Trigger phrasings include "set up a git workflow for my group project", "how should our team branch our repo", "help me resolve this merge conflict", "our repo is a mess after everyone pushed", "how do I do a pull request properly", "I force-pushed and lost commits", "how do I recover a deleted branch", and exact error signatures such as "CONFLICT (content): Merge conflict in", "Automatic merge failed; fix conflicts and then commit the result", "Your branch and 'origin/main' have diverged", "error: failed to push some refs", "fatal: refusing to merge unrelated histories", and "Already up to date" confusion. Also activate for PR template requests, .gitignore/.gitattributes setup for student projects, and branch protection rule questions.

  • Reads credentials
  • Deletes or force-pushes
  • Installs packages
  • Commits and pushes

The file

Show its rules and text

We split this skill into the rules it gives an agent

22 rules. About 0 are common, 19 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈19

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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.