Edit DataSurface model fragment

Update a DataSurface model fragment and create a pull request.

2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/datasurface/demo1 --skill edit-datasurface-model-fragment-datasurface
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Edit DataSurface model fragment
Source: https://github.com/datasurface/demo1/tree/main/.claude/skills/edit-model-fragment
Command: npx skills add https://github.com/datasurface/demo1 --skill edit-datasurface-model-fragment-datasurface

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you update a DataSurface model fragment by pulling the latest from main, applying edits, and pushing to the owningRepo branch to create a PR.

Core Features & Use Cases

  • Edit GCO components: Modify Team, GovernanceZone, RTE, or PSP code in their respective repos.
  • Branching & PR workflow: Create a fresh owningRepo branch, push changes, and auto-trigger a PR to main for review.
  • Auditable process: All edits are tracked through Git history and PR reviews, ensuring governance.

Quick Start

Start from main, create a feature branch for your owningRepo, edit files, and push to trigger a PR.

Frequently Asked Questions about Edit DataSurface model fragment

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

FAQPage Schema
How do I edit a DataSurface model fragment and submit changes for review?

Pushing edits to the owningRepo branch automatically creates a PR to main. This workflow pulls the latest main, applies your changes, and submits them for governance review.

What is the Git workflow for modifying GCO components like Team or GovernanceZone?

The Git workflow for modifying GCO components involves starting from main, creating a fresh feature branch, editing the files, and pushing to trigger a PR. This ensures all changes are tracked and auditable.

Do I need external dependencies to push DataSurface model fragment edits via PR?

You do not need external dependencies beyond standard Git tooling to push model fragment edits. You only require appropriate repository permissions to create branches and push changes.

When should I use an automated PR workflow for DataSurface model fragments?

Use an automated PR workflow for DataSurface model fragments when modifying GCO components like Team, GovernanceZone, RTE, or PSP. It ensures governance by tracking all edits through Git history and review.

Can I push model fragment edits directly to the main branch?

You cannot push model fragment edits directly to main. Edits must be pushed to a fresh owningRepo branch to auto-trigger a PR to main, ensuring changes are reviewed for governance.