How do I install the Sc Managing Worktrees skill?

Run npx skillmds@latest add tomevault-io/sc-managing-worktrees in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sc Managing Worktrees safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sc Managing Worktrees?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sc Managing Worktrees free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sc Managing Worktrees?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sc Managing Worktrees by tomevault-io

Name: Sc Managing Worktrees
Author: tomevault-io

File contents

Managing Git Worktrees

Use this skill to manage worktrees with a standard structure and tracking. Use the /sc-git-worktree command to invoke this skill.

Agent Delegation (Required)

This skill delegates all execution to specialized agents via the Task tool (no manual git commands in the primary session). Always pass inputs via <input_json> and render <output_json> from the subagent response.

Task tool template:

<invoke name="Task">
<parameter name="subagent_type">$SUBAGENT</parameter>
<parameter name="description">$DESCRIPTION</parameter>
<parameter name="prompt">Run $SUBAGENT with this input:

<input_json>
```json
$INPUT_JSON

Operation	Agent	Returns
Create	`sc-worktree-create`	JSON: success, path, branch, tracking_entry
Scan	`sc-worktree-scan`	JSON: success, worktrees list, recommendations
Cleanup	`sc-worktree-cleanup`	JSON: success, branch_deleted, tracking_update
Abort	`sc-worktree-abort`	JSON: success, worktree_removed, tracking_update
Update	`sc-worktree-update`	JSON: success, commits_pulled, conflicts (if any)

To invoke an agent, use the Task tool with the agent prompt and pass parameters exactly as documented in the agent Inputs section.

Standards and Paths

Repo root: current directory.
Default worktree base: ../{{REPO_NAME}}-worktrees.
Worktrees live in <worktree_base>/<branch>.
Tracking file (if used): <worktree_base>/worktree-tracking.jsonl must be updated on create/scan/cleanup/abandon. Allow a toggle to disable tracking for repos that don't use it.
Naming: worktree directory = branch name; branch naming follows repo policy.
Branch protections/hooks: no direct commits to protected branches.

Protected Branch Configuration

Protected branches (main, develop, master, etc.) require special handling to prevent accidental deletion:

# .sc/shared-settings.yaml
git:
  protected_branches:
    - "main"
    - "develop"
    - "master"

Protected Branch Rules:

Protected branches are read from .sc/shared-settings.yaml (git.protected_branches)
If missing, protected branches are auto-detected from git-flow and cached to .sc/shared-settings.yaml
Cleanup/abort agents NEVER delete protected branches (local or remote)
Protected branches can only be removed from worktrees, never deleted
Use --update to safely pull changes for protected branches in worktrees

Safety and reminders

NEVER delete protected branches (main, develop, master) under any circumstances.
Protected branches can only be removed from worktrees; the branch itself must always be preserved.
Never delete branches or force-remove worktrees without explicit approval.
Never clean/abandon a worktree with uncommitted changes unless explicitly approved.
Keep tracking JSONL in sync on every operation when enabled.
Respect branch protections and hooks; no direct commits to protected branches.
Use background agents for worktree operations; keep the main context focused on decisions and summaries.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: sc-managing-worktreesdescription: This skill delegates all execution to specialized agents via the **Task tool** (no manual git commands in the primary session). Use when this capability is needed.---# Managing Git WorktreesUse this skill to manage worktrees with a standard structure and tracking. Use the `/sc-git-worktree` command to invoke this skill.## Agent Delegation (Required)This skill delegates all execution to specialized agents via the **Task tool** (no manual git commands in the primary session).Always pass inputs via `<input_json>` and render `<output_json>` from the subagent response.**Task tool template:**```xml<invoke name="Task"><parameter name="subagent_type">$SUBAGENT</parameter><parameter name="description">$DESCRIPTION</parameter><parameter name="prompt">Run $SUBAGENT with this input:<input_json>```json$INPUT_JSON```</input_json></parameter></invoke>```| Operation | Agent | Returns ||-----------|-------|---------|| Create | `sc-worktree-create` | JSON: success, path, branch, tracking_entry || Scan | `sc-worktree-scan` | JSON: success, worktrees list, recommendations || Cleanup | `sc-worktree-cleanup` | JSON: success, branch_deleted, tracking_update || Abort | `sc-worktree-abort` | JSON: success, worktree_removed, tracking_update || Update | `sc-worktree-update` | JSON: success, commits_pulled, conflicts (if any) |To invoke an agent, use the Task tool with the agent prompt and pass parameters exactly as documented in the agent Inputs section.## Standards and Paths- Repo root: current directory.- Default worktree base: `../{{REPO_NAME}}-worktrees`.- Worktrees live in `<worktree_base>/<branch>`.- Tracking file (if used): `<worktree_base>/worktree-tracking.jsonl` must be updated on create/scan/cleanup/abandon. Allow a toggle to disable tracking for repos that don't use it.- Naming: worktree directory = branch name; branch naming follows repo policy.- Branch protections/hooks: no direct commits to protected branches.## Protected Branch ConfigurationProtected branches (main, develop, master, etc.) require special handling to prevent accidental deletion:```yaml# .sc/shared-settings.yamlgit: protected_branches: - "main" - "develop" - "master"```**Protected Branch Rules:**- Protected branches are read from `.sc/shared-settings.yaml` (`git.protected_branches`)- If missing, protected branches are auto-detected from git-flow and cached to `.sc/shared-settings.yaml`- **Cleanup/abort agents NEVER delete protected branches** (local or remote)- Protected branches can only be removed from worktrees, never deleted- Use `--update` to safely pull changes for protected branches in worktrees## Safety and reminders- **NEVER delete protected branches** (main, develop, master) under any circumstances.- Protected branches can only be removed from worktrees; the branch itself must always be preserved.- Never delete branches or force-remove worktrees without explicit approval.- Never clean/abandon a worktree with uncommitted changes unless explicitly approved.- Keep tracking JSONL in sync on every operation when enabled.- Respect branch protections and hooks; no direct commits to protected branches.- Use background agents for worktree operations; keep the main context focused on decisions and summaries.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/randlee) — claim your Tome and manage your conversions.

Frequently asked questions

Sc Managing Worktrees