git-workflow
/git-workflow
Safely inspect and perform everyday Git work: branches, focused commits, history, integration, conflicts, worktrees, and recovery. Use for local version-control tasks that are not GitHub settings or release publication.
- Author
- gaelic-ghost ↗
- Repository
- socket ↗
- Licence
- Apache-2.0
- Last repository change
- 26.08.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Safely inspect and perform everyday Git work: branches, focused commits, history, integration, conflicts, worktrees, and recovery. Use for local version-control tasks that are not GitHub settings or release publication.
Original author description
Safely inspect and perform everyday Git work: branches, focused commits, history, integration, conflicts, worktrees, and recovery. Use for local version-control tasks that are not GitHub settings or release publication.
How it works
- Purpose
- Workflow
- Boundaries
- Hermes Notes
SKILL.md preview
--- name: git-workflow description: "Safely inspect and perform everyday Git work: branches, focused commits, history, integration, conflicts, worktrees, and recovery. Use for local version-control tasks that are not GitHub settings or release publication." --- # Git Workflow ## Purpose Handle ordinary local Git work with enough evidence to preserve uncommitted work, branch reachability, and worktree ownership. This workflow does not own GitHub settings or protected-main releases. ## Workflow 1. Read the closest `AGENTS.md`; inspect `git status --short --branch`, `git worktree list`, and the relevant history/diff before a mutation. 2. Inspect the effective Git configuration before an operation depends on fetch, pull, or tracking-branch behavior. On Gale-managed machines, expect `fetch.prune=true`, `pull.ff=only`, and `branch.autoSetupRebase=always`; report any local or worktree override rather than silently changing it. See `references/gale-git-baseline.md`. 3. Classify the operation: - inspection: status, diff, log, blame, or reachability; - focused change: create/switch a branch, stage intentional files, commit; - integration: fetch, compare, rebase or merge, resolve conflicts; - recovery: reflog, lost commit investigation, or safe restoration plan. 4. Preserve the current work before an operation that rewrites, discards, or moves it. Explain the exact target and recovery path before using reset, clean, rebase, force push, or branch/worktree deletion. 5. For branch work, use a feature branch and separate worktree when required by repository guidance. Never keep the same branch live in two worktrees except as a short recovery step. 6. Make focused commits with the repository's required subject format. Review staged changes and commit reachability after each shared Git mutation. 7. For integration, fetch first. The normal Gale baseline prunes stale refs and refuses pull-created merge commits; newly tracking branches rebase on pull. Choose a merge or rebase only when repository policy and the branch's publication state justify it. Resolve each conflict from source intent, run proportionate validation, and inspect the resulting diff. 8. Before deleting a branch, worktree, ref, or archive, verify reachability and complete any repository-required branch accounting. ## Boundaries - Route GitHub pull requests, reviews, issues, and CI collaboration to `github-collaboration-workflow`. - Route tags, publishing, GitHub releases, and protected-main release cleanup to `maintain-project-repo`. - Route GitHub settings, rulesets, and security configuration to `maintain-github-repository`. - Push, force push, merge, tag, and destructive recovery actions require clear user authority or an existing repository-owned release contract. - Do not encode Gale's machine-level Git baseline as repository-local config in a generated template or existing repository. ## Hermes Notes This is portable guidance. Verify that `git` is installed, the target is a Git worktree, and the active identity/remotes are the intended ones. Hermes gains no Git credentials or mutation authority from this skill.
Files in this package (3)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
- references/gale-git-baseline.md 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · gaelic-ghost/socket | 90 | Apache-2.0 |
| event4u-app/agent-config | 100 | MIT |
| lee-w/maigo | 100 | MIT |
| hakula139/plugins | 100 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| eliyce/paqad-ai | 100 | MIT |
| langfuse/langfuse | 100 | MIT |
| Muvon/octomind-tap | 100 | Apache-2.0 |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 563ff63d1684 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100git
Full git workflow for developers: status, staging, commits, branches, push/pull, merge/rebase, conflict resolution, stash, history (log/blame/bisect), remotes, tags, worktrees, cherry-pick, and recovery with reflog. The everyday operations live in the git tool; this skill covers… - 100git-github
Use for any git or GitHub operation in the team repo — creating the repo from the template, branches, PRs with gh, issues, resolving conflicts, and recovering from mistakes. - 100maisongr-git
Maison GR method for everyday version control. Use when creating branches, staging and committing, writing commit messages, resolving merge conflicts, keeping a branch current, tagging a release, or setting up a repository's Git hygiene (.gitignore, .gitattributes). Checks the… - 100git
Guide for Git operations including commits, branches, rebasing, and conflict resolution. Use when working with version control, creating commits, managing branches, or resolving merge conflicts. - 100git-workflows
Use when handling Git branches, commits, synchronization, merges, rebases, cherry-picks, conflict resolution, or repository recovery. - 100cleanup-git
Remove merged local branches and stale git worktrees. Use when the user says "cleanup branches", "prune worktrees", "tidy git", "remove merged branches", "delete merged branches", "gone branches", or wants to clean local git state. NOT for creating commits, creating worktrees,…