Claude Skill

git-delivery

Stage, commit, push, and release scoped changes with Conventional Commits; fix hook failures.

LLM Mart · 0 points · 2 views 0 listing impressions 0 install-command copies
Download fmind-dot-skills_git-delivery-3bbe830.zip · 10 KB

Install

skills CLI npx skills add https://github.com/fmind/dot/tree/main/skills/git-delivery
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install fmind-dot@llmmart
Git git clone https://github.com/fmind/dot.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole fmind/dot collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Git Delivery

Deliver only authorized changes while preserving the index, branch state, and enabled hooks across branching, commits, pushes, and releases.

Workflow

  1. Confirm authority and target branch: inspect the active branch and unmerged work before switching; never overwrite existing branches or move unrelated commits. History investigation stays read-only (fetch into an isolated clone and bisect in a disposable worktree); pulling or rewriting history requires authority.
  2. Match the requested boundary: commit-only requests keep the staged selection and stop at git commit; delivery requests stage and push only intended changes without publishing a release.
  3. Select branch, PR, or release mode: follow git-worktree and pull-request when requested; for releases, prefer the repository's native release task over manual steps.
  4. Verify delivery: confirm the exact SHA, remote ref, and publication level while keeping published tags immutable and hooks enabled.

Commit messages

  • Write one Conventional Commits subject: <type>(<scope>): <description> using feat, fix, chore, docs, refactor, test, perf, ci, build, style, or revert — imperative, <72 chars, ! before : for breaking changes, and zero AI attribution or Co-authored-by trailers.
  • Commit only staged changes: never auto-stage unrelated files; report hook failures or empty indexes without amending.

Task guides

  • git-add-commit-push: Stage, commit, push, and recover hook failures within the authorized scope.
  • git-worktree: Create Git branches, worktrees, or isolated snapshots of uncommitted work.
  • release: Prepare, publish when requested, or verify versioned releases.
  • resolve-conflicts: Resolve Git merge or rebase conflicts by both sides' intent; verify the result.
Files (dot)
  • references
    • git-worktree
      • GUIDE.md 2.3 KB
        Loading…
    • release
      • references
        • publish.md 2.9 KB
          Loading…
        • verify-assets.md 1.1 KB
          Loading…
        • verify.md 1.5 KB
          Loading…
        • versioning.md 918 B
          Loading…
      • GUIDE.md 2.1 KB
        Loading…
    • git-add-commit-push.md 3 KB
      Loading…
    • resolve-conflicts.md 1.6 KB
      Loading…
  • SKILL.md 2.4 KB
    ---
    name: git-delivery
    description: "Commit, push, and release with Conventional Commits; branches, worktrees, conflicts, and hook fixes."
    license: MIT
    metadata:
      kind: task
      author: Médéric HURIER (Fmind)
      source: github.com/fmind/dot/tree/main/skills/git-delivery
      created: "2026-09-16"
      updated: "2026-11-11"
    ---
    
    # Git Delivery
    
    Deliver only authorized changes while preserving the index, branch state, and enabled hooks across branching, commits, pushes, and releases.
    
    ## Workflow
    
    1. **Confirm authority and target branch**: inspect the active branch and unmerged work before switching; never overwrite existing branches or move unrelated commits. History investigation stays read-only (fetch into an isolated clone and bisect in a disposable worktree); pulling or rewriting history requires authority.
    1. **Match the requested boundary**: commit-only requests keep the staged selection and stop at `git commit`; delivery requests stage and push only intended changes without publishing a release.
    1. **Select branch, PR, or release mode**: follow [git-worktree](references/git-worktree/GUIDE.md) and [pull-request](../gh/references/pull-request.md) when requested; for releases, prefer the repository's native release task over manual steps.
    1. **Verify delivery**: confirm the exact SHA, remote ref, and publication level while keeping published tags immutable and hooks enabled.
    
    ## Commit messages
    
    - **Write one Conventional Commits subject**: `<type>(<scope>): <description>` using `feat`, `fix`, `chore`, `docs`, `refactor`, `test`, `perf`, `ci`, `build`, `style`, or `revert` — imperative, `<72` chars, `!` before `:` for breaking changes, and zero AI attribution or `Co-authored-by` trailers.
    - **Commit only staged changes**: never auto-stage unrelated files; report hook failures or empty indexes without amending.
    
    ## Task guides
    
    <!-- guides:start -->
    
    - [git-add-commit-push](references/git-add-commit-push.md): Stage, commit, push, and recover hook failures within the authorized scope.
    - [git-worktree](references/git-worktree/GUIDE.md): Create Git branches, worktrees, or isolated snapshots of uncommitted work.
    - [release](references/release/GUIDE.md): Prepare, publish when requested, or verify versioned releases.
    - [resolve-conflicts](references/resolve-conflicts.md): Resolve Git merge or rebase conflicts by both sides' intent; verify the result.
    
    <!-- guides:end -->
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.