update-working-copy
Skill20 starsChanged 44 days agoMITView on GitHub
Fetch the latest from the remote. Update the working branch or switch to main if the branch is defunct.
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- breakdownSkill
- bug-investigationSkill
- code-review-adversarialSkill
- code-review-multiSkill
- code-review-with-followupSkill
- document-changesSkill
- grillingSkill
- type-test-codeSkill
- explain-changesSkill
- github-actions-ciSkill
- github-appSkill
- github-ticketsSkill
- implementation-planSkill
- implement-simpleSkill
- implementSkill
- implement-ttcSkill
- orchestrationSkill
- pull-requestSkill
- review-and-wrap-upSkill
- verusSkill
- specSkill
- ticketsSkill
- verifySkill
- wrap-upSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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 8
Make sure the repository is up to date- fetch the latest from the remote.
- Distinctive: line 10
If the remote branch is ahead of the local branch, pull that in.
- Distinctive: line 12
If you are on a branch that is not main:
- Distinctive: line 13
If your branch commits are included in the tip of main (directly or via rebase or squashing), switch to the tip of main
- Distinctive: line 14
If your branch is behind the tip of main, ask the user whether you should merge that in or move to that.
≈ “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.
Files
The defaults we use are remote=origin, branch=main. However, these may have different values in this project.
Make sure the repository is up to date- fetch the latest from the remote.
If the remote branch is ahead of the local branch, pull that in.
If you are on a branch that is not main:
- If your branch commits are included in the tip of
main(directly or via rebase or squashing), switch to the tip ofmain - If your branch is behind the tip of
main, ask the user whether you should merge that in or move to that.
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
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.

