branch-safely
Skill0 starsChanged 4 months agoMITView on GitHub
Use before implementation when checking repository state, selecting a branch, or protecting uncommitted work.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- deployment-decisionsSkill
- deploySkill
- deploy-vercelSkill
- deploy-vpsSkill
- documentationSkill
- e2e-testingSkill
- feature-testingSkill
- monitoringSkill
- orchestrateSkill
- quality-reviewSkill
- requirements-gatheringSkill
- solution-designSkill
- task-breakdownSkill
- ui-uxSkill
- unit-testingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
Before modifying code, check whether the project is a Git repository.
≈ “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
Branch Safely
Before modifying code, check whether the project is a Git repository.
For an existing repository, inspect project conventions, git status, and the current branch. Never discard, reset, or overwrite unrelated work. Never work directly on main or master; create a task feature branch before implementation. Report the branch and pre-existing changes.
Treat git status, git diff, git log, git branch, git show, git remote -v, normal branch creation or switching without force, and git add as routine local work. Require explicit human approval before git commit; any push, pull, fetch, remote, or tag operation; merge, rebase, reset, restore, clean, force switch, or branch deletion. Never expose credentials from remotes, configuration, or protected files.
For a directory that is not a Git repository, run git init -b main automatically. Do not set global Git identity. Do not create a commit automatically — commits require an explicit human request. Before an initial baseline commit, check local Git identity and ask the human to configure it if absent. A newly initialized repository may remain on main until that requested baseline commit; after that, create a task feature branch before implementation.
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.