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)
git checkout -b feature-name
Commit changes
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:
# 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:
# make changes...
git add <files>
git commit -m "fix: address review feedback"
Commit Message Conventions
Use Conventional Commits format:
feat:— new featurefix:— bug fixdocs:— documentation onlyrefactor:— code change that neither fixes nor addstest:— adding or updating testschore:— maintenance tasks
This skill intentionally avoids any gh or PR commands to prevent accidental pushes or PR creation.
Source: sbfaulkner/pi-extensions — distributed by TomeVault.