branch-safely

Files (1)

• SKILL.md

SKILL.md (first lines)

# 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.

From prinx/agents, MIT.

More from prinx/agents