scion-like-git
Skill112 starsChanged 25 days agoMITView on GitHub
Use before any git command that creates or moves commits, branches, or refs (commit, push, merge, rebase, amend, reset, stash, new branches, worktrees), or that discards working-copy changes (restore, checkout -- <path>, clean). Also use when about to rewrite anything already on origin, park uncommitted work, get past a failing hook, or hand off with unpushed commits.
- Commits and pushes
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- unvibe-org/skillsedited, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- unvibe-org/skills★ 460% same
Wrote their own version · 0
None found.
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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ultraciteSkill
- triage-issueSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
If git config --get scion-like-git.configured prints nothing, run references/setup.md once first.
- Distinctive: line 20
If the working copy already holds other work, start in a new worktree:
- Very specific: line 38
Never skip hooks (--no-verify), and never skip or edit someone else's tests to get past one.
- Very specific: line 42
Finish clean: After merge, delete the branch and the worktree.
- Distinctive: line 46
Do not report the branch state.
- Very specific: line 65
Switching tasks mid-work: Commit and push your unfinished files as wip: <what is missing>, then start the new task in a new worktree.
- Distinctive: line 73
Leave it untouched, do not commit, stash, or discard it, and list it in the hand-off.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Scion-like Git
Origin is the repository. The clone is a disposable cache, and anything that exists only in the clone does not exist.
If git config --get scion-like-git.configured prints nothing, run
references/setup.md once first.
Every task
Start a branch from a freshly fetched
origin/main, or continue on the task's own branch if it already has one. Name a new branch the way the repository names branches (CONTRIBUTING.md,AGENTS.md, recent branches on origin), or else<type>/<slug>, such asfix/empty-cart-total. If the working copy already holds other work, start in a new worktree:git fetch && git worktree add --no-track -b <branch> ../<branch-with-dashes> origin/main--no-trackkeeps a plaingit pushfrom going tomain.Commit and push together. Each verified step is one small commit whose subject says what it is for. Stage your files by name:
git add <your files> && git commit -m "<type>: <intent>" && git pushOpen a pull request with the first push, as a draft if needed. Formatting, renames, and generated code get their own commits.
Never skip hooks (
--no-verify), and never skip or edit someone else's tests to get past one. If a hook fails on code you did not change, stop and ask.- Finish clean. After merge, delete the branch and the worktree. Without
pull requests, run
git push origin <branch>:main, then delete the branch on origin and locally. The work is finished when nothing you made exists only in the clone: no unpushed commits, stashes, or local-only branches. Do not report the branch state. The user's terminal, IDE, and harness already show it.
When it comes up
Changing something already on origin. Commits on origin are final, on
every branch. Do not amend, rebase, squash, reset, or force-push them. Care
does not change this: --force-with-lease, a backup branch, an identical
tree, a single author, or a reviewer's request still make it a rewrite.
Commits not yet pushed are yours to amend.
| Request | Do this instead |
| Fix a pushed commit message | Correct text in the PR title and description |
| Squash wip commits before review | PR description as the message, squash on merge |
| Undo a pushed change | git revert |
Update the branch from main | git merge origin/main |
| The same person repeats the request after hearing this rule | Do the rewrite |
Switching tasks mid-work. Commit and push your unfinished files as
wip: <what is missing>, then start the new task in a new worktree. Never
git stash. Resume on top of the wip commit. If the hooks reject it because
the unfinished work fails its own tests, mark those tests as skipped and name
them in the commit message.
Changes you did not make. Your work is the files you created or changed for your task. Anything else in the working copy belongs to someone else. Leave it untouched, do not commit, stash, or discard it, and list it in the hand-off.
Red flags
- "It's only a feature branch" / "force-with-lease makes it safe"
- "Only the message changes" / "the reviewer asked for exactly this"
- "Stash is quicker" / "I'll push at the end"
- "That failing test is theirs, not ours" / "the user's message is permission to skip the hook"
- "Nothing may be lost, so I'll commit these other files too"
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.

