sk-git

Orchestrate git workflows with worktrees, deterministic commits, and PR finishes.

31|3|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/MichelKerkmeester/opencode--spec-kit-skilled-agent-orchestration --skill sk-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sk-git
Source: https://github.com/MichelKerkmeester/opencode--spec-kit-skilled-agent-orchestration/tree/main/.opencode/skill/sk-git
Command: npx skills add https://github.com/MichelKerkmeester/opencode--spec-kit-skilled-agent-orchestration --skill sk-git

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill coordinates complex git workflows by providing an integrated orchestration layer that manages workspace isolation, deterministic commit messages, artifact filtering, and a safe finish flow. It guides through a three-phase lifecycle: workspace setup, work and commit, and complete and integrate, routing the appropriate references and templates as needed.

Core Features & Use Cases

  • Unified workflow orchestration for git worktrees, commits, and PR finishes.
  • Deterministic commits with first-match type/scope logic to ensure consistent history.
  • Artifact filtering to prevent non-public files from entering the history.
  • Structured routing across phases with memory continuity and MCP integration for remote actions.
  • Use Case: A solo feature can be developed in an isolated worktree, committed cleanly, then finished with a PR and cleanup.

Quick Start

Invoke sk-git to coordinate workspace setup, commits, and finish steps by describing your git task or triggering a routing.

Frequently Asked Questions about sk-git

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate git worktree workflows for isolated feature development?

Git worktree workflows can be automated by routing tasks through an orchestrator that enforces a three-phase lifecycle: workspace setup, work and commit, and complete and integrate. This ensures consistent workspace isolation and safe PR finishes.

How do I ensure deterministic conventional commits across multiple git worktrees?

Deterministic conventional commits are enforced using first-match type and scope logic within the commit phase. This routing ensures commit messages remain consistent across isolated worktrees and team initiatives without manual formatting.

Can I use GitHub MCP integrations to manage PR workflows from an isolated worktree?

Yes, GitHub MCP integrations are supported for remote actions during the finish phase. This allows you to manage PR workflows and cleanup directly from the orchestrator after completing work in your isolated worktree.

What is the best way to prevent non-public files from entering git history?

Artifact filtering prevents non-public files from entering git history during the commit phase. This enforces a strict protocol via frontmatter-driven routing to ensure only appropriate artifacts are committed to the repository.

Does a git worktree orchestrator work for solo projects as well as team initiatives?

Yes, git worktree orchestration applies to both solo projects and team initiatives. It routes the appropriate references and templates across the three-phase process with memory continuity to manage the full development lifecycle.