# Git Workflow

> Local git workflow guidance for repositories with no remote configured. Use when there is no origin remote and PRs are not possible. Use when this capability is needed.

- Skill: `tomevault-io/git-workflow-127` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/git-workflow-127`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/git-workflow-127/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/git-workflow-127

---


# Local Git Workflow (no remote)

This skill documents safe, local git workflows for repositories that do not have a remote configured. It intentionally omits PR instructions to avoid accidental remote operations.

## Core Principles

- Work locally using branches and commits.
- Keep changes small and focused.
- Write clear commit messages describing what and why.

## Workflow

### Start a feature (local)

```bash
git checkout -b feature-name
```

### Commit changes

```bash
git add <files>           # stage specific files
git commit -m "feat: description of change"
```

### If you later add a remote

If you configure an origin remote later (e.g., `git remote add origin <url>`), follow the GitHub PR guidance in the `github-workflow` skill.

### Update from main (local)

When working locally, you can rebase or merge as appropriate for your workflow. If a remote is later added, prefer rebasing onto the remote `main` for a clean history:

```bash
# If a remote exists later:
git fetch origin
git rebase origin/main
```

### Address review feedback (local)

Collect feedback outside of GitHub (e.g., chat), then:

```bash
# make changes...
git add <files>
git commit -m "fix: address review feedback"
```

## Commit Message Conventions

Use [Conventional Commits](https://www.conventionalcommits.org/) format:

- `feat:` — new feature
- `fix:` — bug fix
- `docs:` — documentation only
- `refactor:` — code change that neither fixes nor adds
- `test:` — adding or updating tests
- `chore:` — maintenance tasks


This skill intentionally avoids any `gh` or PR commands to prevent accidental pushes or PR creation.

---
> Source: [sbfaulkner/pi-extensions](https://github.com/sbfaulkner/pi-extensions) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-06-16 -->