How do I install the Workspace Git Management Devforge skill?

Run npx skillmds@latest add construct-ai-primary/workspace-git-management-devforge 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 Workspace Git Management Devforge safe to use?

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

Which AI agents work with Workspace Git Management Devforge?

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 Workspace Git Management Devforge free to use?

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

Who published Workspace Git Management Devforge?

Construct-AI-primary (@construct-ai-primary) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Workspace Git Management Devforge by construct-ai-primary

Name: Workspace Git Management Devforge
Rating: 4.2 (5 reviews)
Author: Construct-AI-primary

Workspace Git Management Devforge

Use when managed workspace git clone race conditions occur, isolated_workspace fails on first use, worktree creation crashes, or git repository initialization issues block agent heartbeats. Handles ensureManagedProjectWorkspace and realizeExecutionWorkspace.

Construct-AI-primary Updated Sep 8, 2026 0 repo stars

File contents

Workspace Git Management - DevForge AI

Overview

Handles workspace and git management issues in the Paperclip codebase. Resolves managed workspace git clone race conditions, isolated_workspace failures on first use, worktree creation crashes, and git repository initialization issues that block agent heartbeats.

When to Use

When fatal: not a git repository error occurs during first agent heartbeat
When ensureManagedProjectWorkspace returns success with warning for non-git directory
When realizeExecutionWorkspace crashes at git rev-parse --show-toplevel
When sourceType: "git_repo" with isolated_workspace policy fails
When worktree creation fails on incomplete clone
Don't use when: It's a general git connectivity issue (use cloudops-devforge-cloud-operations)

Core Procedures

Workspace Clone Fix Workflow

Identify Race Condition - Check if clone completed before workspace resolution
Validate Git Repo - Ensure baseCwd has .git directory before worktree ops
Fix Clone Logic - Make ensureManagedProjectWorkspace throw on missing clone, not warn
Add Pre-Check - Verify baseCwd is valid git repo before realizeExecutionWorkspace
Test First-Use - Verify workspace works on first heartbeat, not just subsequent ones

Common Failure Points

ensureManagedProjectWorkspace returns success for existing non-git directory (lines 175-183)
realizeExecutionWorkspace runs git rev-parse before clone completes (line 590)
Lazy clone means first heartbeat always fails, second succeeds with fallback

Agent Assignment

Primary Agent: cloudops-devforge-cloud-operations Company: DevForge AI Role: Workspace Git Specialist Reports To: cloudops-devforge-cloud-operations Backup Agents: devcore-devforge-core-development, codesmith-devforge-backend-engineer

Success Metrics

First heartbeat succeeds with git_repo sourceType
No fallback to shared_workspace when isolated_workspace configured
Clone completes before workspace resolution
Worktree creation always succeeds

Error Handling

Error: Clone fails (invalid URL, network issue) Response: Surface error immediately, don't return success with warning
Error: Worktree creation fails on existing directory Response: Clean directory, retry clone, or provide eager provisioning API

Cross-Team Integration

Gigabrain Tags: devforge, workspace, git, clone, worktree, isolated-workspace Related Skills: cloudops-devforge-cloud-operations, devcore-devforge-core-development, codesmith-devforge-backend-engineer Last Updated: 2026-04-07

---name: workspace-git-management-devforgedescription: Use when managed workspace git clone race conditions occur, isolated_workspace fails on first use, worktree creation crashes, or git repository initialization issues block agent heartbeats. Handles ensureManagedProjectWorkspace and realizeExecutionWorkspace.---# Workspace Git Management - DevForge AI## OverviewHandles workspace and git management issues in the Paperclip codebase. Resolves managed workspace git clone race conditions, isolated_workspace failures on first use, worktree creation crashes, and git repository initialization issues that block agent heartbeats.## When to Use- When `fatal: not a git repository` error occurs during first agent heartbeat- When `ensureManagedProjectWorkspace` returns success with warning for non-git directory- When `realizeExecutionWorkspace` crashes at `git rev-parse --show-toplevel`- When `sourceType: "git_repo"` with `isolated_workspace` policy fails- When worktree creation fails on incomplete clone- **Don't use when:** It's a general git connectivity issue (use cloudops-devforge-cloud-operations)## Core Procedures### Workspace Clone Fix Workflow1. **Identify Race Condition** - Check if clone completed before workspace resolution2. **Validate Git Repo** - Ensure `baseCwd` has `.git` directory before worktree ops3. **Fix Clone Logic** - Make `ensureManagedProjectWorkspace` throw on missing clone, not warn4. **Add Pre-Check** - Verify `baseCwd` is valid git repo before `realizeExecutionWorkspace`5. **Test First-Use** - Verify workspace works on first heartbeat, not just subsequent ones### Common Failure Points- `ensureManagedProjectWorkspace` returns success for existing non-git directory (lines 175-183)- `realizeExecutionWorkspace` runs `git rev-parse` before clone completes (line 590)- Lazy clone means first heartbeat always fails, second succeeds with fallback## Agent Assignment**Primary Agent:** cloudops-devforge-cloud-operations**Company:** DevForge AI**Role:** Workspace Git Specialist**Reports To:** cloudops-devforge-cloud-operations**Backup Agents:** devcore-devforge-core-development, codesmith-devforge-backend-engineer## Success Metrics- First heartbeat succeeds with git_repo sourceType- No fallback to shared_workspace when isolated_workspace configured- Clone completes before workspace resolution- Worktree creation always succeeds## Error Handling- **Error:** Clone fails (invalid URL, network issue) **Response:** Surface error immediately, don't return success with warning- **Error:** Worktree creation fails on existing directory **Response:** Clean directory, retry clone, or provide eager provisioning API## Cross-Team Integration**Gigabrain Tags:** devforge, workspace, git, clone, worktree, isolated-workspace**Related Skills:** cloudops-devforge-cloud-operations, devcore-devforge-core-development, codesmith-devforge-backend-engineer**Last Updated:** 2026-04-07

Frequently asked questions