skills.rest
billynewport
billynewportCOMMUNITY
Explore all skills by this author →
Website𝕏@billynewportGitHub

Edit DataSurface model fragment

Edit DataSurface model fragments on an owningRepo branch and open a PR.

1|Updated Feb 6, 2026
Search Tags:#git#pull-request#version-control#model-fragment#owningRepo#DataSurface
One-click install
npx skills add https://github.com/billynewport/demo_cokub_model --skill edit-datasurface-model-fragment
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Edit DataSurface model fragment
Source: https://github.com/billynewport/demo_cokub_model/tree/main/.claude/skills/edit-model-fragment
Command: npx skills add https://github.com/billynewport/demo_cokub_model --skill edit-datasurface-model-fragment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams modify DataSurface model fragments by providing a repeatable, PR-driven workflow that keeps ownership clean and reduces merge conflicts.

Core Features & Use Cases

  • Controlled edits: Create and switch to an owningRepo branch to isolate changes.
  • PR-driven workflow: Commit and push changes to trigger a PR against main for review.
  • Safe collaboration: Step-by-step workflow enforces ownership and traceability.

Quick Start

Use this skill to fetch the latest main, edit the relevant model fragment files, create a fresh owningRepo branch, commit changes, and push to origin to open 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 a pull request?▼

To edit a DataSurface model fragment, pull the latest main, modify the fragment files, create an owningRepo branch, commit, and push to origin to trigger a PR against main for review.

What is the owningRepo branch workflow for DataSurface model changes?▼

The owningRepo branch workflow isolates DataSurface model fragment changes by switching to a dedicated branch before committing, ensuring clean ownership and reducing merge conflicts when pushing to trigger a pull request.

How do I avoid merge conflicts when updating DataSurface model fragments?▼

Avoid merge conflicts during DataSurface model fragment updates by pulling the latest main before editing, isolating changes on a fresh owningRepo branch, and using a PR-driven review process to manage collaborative modifications.

Can I push DataSurface model changes directly to main without a pull request?▼

No, DataSurface model fragment modifications require a PR-driven workflow where you push an owningRepo branch to origin, triggering a pull request against main to enforce ownership constraints and traceability through review.

What are the branch ownership constraints for DataSurface model fragments?▼

Branch ownership constraints require DataSurface model fragment edits to be committed to a specific owningRepo branch rather than main, isolating changes and enforcing a PR-driven review process to maintain clean collaborative version control.

Why does my DataSurface model fragment edit require an owningRepo branch?▼

An owningRepo branch is required for DataSurface model fragment edits to isolate changes, maintain clear ownership, and enable a PR-driven review process that reduces merge conflicts when collaborating on version-controlled models.

Related Skills

Explore More Software Engineering Skills→
datasurfacedatasurface

Edit DataSurface model fragment

Update a DataSurface model fragment and create a pull request.

Official
Intermediate
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
GolferGeekGolferGeek

GitHub Workflow

Standardize GitHub branching, pull requests, code reviews, and CI/CD pipelines.

Community
Basic
RedBoardDevRedBoardDev

pr-summary

Generates PR titles and descriptions from git branch diffs and commit history.

Community
Basic