agentsclimarketplace

Ow dev git

Skill kaixun96/dev.AgentOW/skills/ow-dev-git

Must invoke this skill if use/match: git, branch, checkout, merge, fetch, pull, commit, push, branch naming, feature branchFrom its SKILL.md

Install
npx -y skills add kaixun96/dev.AgentOW --skill ow-dev-git

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

odsp-web Git Conventions

CRITICAL RULES

  • ALL branches MUST follow: user/<alias>/<feature-name>
  • ALWAYS branch from a fresh origin/main (fetch first) — never from whatever branch you happen to be on
  • NEVER commit directly to main
  • ALWAYS run rush install after switching branches or pulling changes
  • VERIFY the new branch's merge-base equals origin/main HEAD before adding any commit — if it doesn't, the eventual PR diff will include the inverse of every commit landed on main since your stale starting point (one batch run lost this and produced a 145-file PR for a 3-file fix)

Branch Workflow

# 1. Fetch latest main
git fetch origin main

# 2. Create (or reset) the feature branch off the freshly-fetched origin/main.
#    `-B` (capital) creates the branch, or resets it to origin/main if it already
#    exists from a previous run — guarantees a clean merge-base regardless of the
#    branch you were on when this started.
git checkout -B user/<alias>/<feature-name> origin/main

# 3. Verify the merge-base is origin/main HEAD (the two SHAs MUST match):
git merge-base origin/main HEAD
git rev-parse origin/main

# 4. Install deps (required after branch switch)
rush install

Naming Convention

Format: user/<alias>/<feature-name>

Examples:

  • user/kaixun/fix-elevation-mobile
  • user/kaixun/add-photo-grid-resize
  • user/kaixun/update-sp-pages-config

Rules:

  • <alias> = your Microsoft alias (e.g. kaixun)
  • <feature-name> = lowercase, hyphen-separated, descriptive
  • No spaces, no uppercase, no special characters

Common Operations

# Check current branch
git rev-parse --abbrev-ref HEAD

# See changes
git status --short
git diff --stat

# Stage and commit
git add <files>
git commit -m "descriptive message"

# Push to remote
git push -u origin user/<alias>/<feature-name>

# Diff against main
git diff origin/main...HEAD --stat

Gotchas

  • After git checkout or git pull, always run rush install — dependencies may have changed.
  • If rush install tells you to run rush update, do that instead.
  • Use git diff origin/main...HEAD (three dots) for branch comparison.
  • Never force-push to shared branches without confirming with the user first.

Keep looking

Skills are one crate of 608,666. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.