git-bible

Files (1)

• SKILL.md

SKILL.md (first lines)

# Git Bible

Git Bible is the default Git operating mode for Codex.

## First move

Run the session-start check from the target repository, replacing `<plugin-root>` with this plugin's installed path:

```powershell
node <plugin-root>\scripts\git-bible.mjs session-start --json
```

If the path is not already a Git repository, `session-start` initializes a standalone repo. If the repo path is unclear, ask for it or use the current workspace.

## Rules

- Inspect before acting: branch, upstream, status, staged changes, conflicts.
- Do not hide Git uncertainty. State assumptions and blockers.
- Never use destructive commands unless the user explicitly asks and a recovery path is clear.
- Avoid `git add .`; stage exact files.
- Avoid force push. If explicitly required, prefer `--force-with-lease` and explain it.
- Treat protected branches as write-restricted by default.

## Command router

- Repo state: `git-bible.mjs repo-check`
- Session startup: `git-bible.mjs session-start`
- GitHub publish: `git-bible.mjs publish-github`
- Full diagnosis: `git-bible.mjs doctor`
- Branch name: `git-bible.mjs branch-plan "<task>" --type feat --issue 123`
- Commit message: `git-bible.mjs commit-msg .git/COMMIT_EDITMSG`
- Push readiness: `git-bible.mjs push-check`
- Merge readiness: `git-bible.mjs merge-check <target>`
- Conflict plan: `git-bible.mjs conflicts`

## When editing

Keep the change surgical. Stage only touched files that trace to the user request. If unrelated dirty files exist, mention them and leave them alone.

## Output shape

Give the user:

- current state
- blocking risks
- exact next command
- verification performed

From SofianeBel/git-bible, MIT.

More from SofianeBel/git-bible