physicslab_worktrees — community physicslab_worktrees, Science-Lab, AhmedAlnasser2000, community, ai agent skill, ide skills, agent automation, AI agent skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing efficient Git worktree management and branch automation. Start and clean PhysicsLab slice branches safely using git worktrees. Use when asked to create/start a slice branch (for example V5.5d2), start a milestone branch, or create a new worktree.

AhmedAlnasser2000 AhmedAlnasser2000
[0]
[0]
Updated: 3/12/2026

Quality Score

Top 5%
23
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
> npx killer-skills add AhmedAlnasser2000/Science-Lab/physicslab_worktrees
Supports 19+ Platforms
Cursor
Windsurf
VS Code
Trae
Claude
OpenClaw
+12 more

Agent Capability Analysis

The physicslab_worktrees skill by AhmedAlnasser2000 is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Perfect for Development Agents needing efficient Git worktree management and branch automation.

Core Value

Empowers agents to automate tasks such as starting new slice/milestone branches and enforcing best practices using PowerShell scripts like `start_slice_worktree.ps1`, while reminding users to work within created worktree folders and following safe defaults like `fetch + ff-only pull` for local `main` vs `origin` branches.

Capabilities Granted for physicslab_worktrees

Automating new slice/milestone branch creation
Managing worktrees efficiently with safe defaults
Enforcing best practices for Git workflow

! Prerequisites & Limits

  • Requires PowerShell execution capabilities
  • Git repository access needed
  • Limited to specific branch naming conventions (e.g., `work/vX.Yz`)
Project
SKILL.md
4.1 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

PhysicsLab Worktrees

Use this skill when the user asks to start a new slice/milestone branch or create a worktree.

Behavior

  1. If branch name is missing, ask for it.
  2. Start with safe defaults (no push):
    • powershell ./tools/dev/start_slice_worktree.ps1 -Branch work/vX.Yz
  3. Remind the user:
    • Do all work inside the created worktree folder.
    • Push is disabled unless explicitly requested (-Push).
    • The start script enforces fetch + ff-only pull for local main vs origin/main; if main is ahead/diverged, repair main first.
  4. Before wrapping up a slice, always provide:
    • one suggested PR title based on what was actually achieved in committed slice changes
    • a descriptive PR summary/body that covers all major change themes in that branch/slice.
  5. If hot-reload gate workflow is active for the slice:
    • start/maintain tools/dev/slice_session.py artifacts under .slice_tmp/<slice_id>/
    • run gates sequentially by default (one gate, stop for user confirmation)
    • only batch multiple gates when the user explicitly asks
    • classify mid-gate changes and split into follow-up gates when scope/risk expands
    • keep commit messages non-ambiguous with explicit follow-up suffixes when repeating scope.
  6. Before any push, enforce pre-push confirmation:
    • print push plan with branch, upstream target, and commits to be pushed
    • verify branch/slice match
    • wait for explicit user approval
    • if unclear, commit locally only and do not push.
  7. Enforce same-slice branch containment:
    • keep all slice changes (code/docs/policies/tests/tweaks) on the same slice branch
    • verify current branch against .physicslab_worktree.json when available
    • if mismatch is detected, stop and present recovery plan before any commit/push
    • do not push mixed-slice commit batches.
  8. Enforce no-leftover-commits + main-sync timing:
    • at slice handoff (or before switching slices), run/report:
      • git status --short
      • git log --oneline @{u}.. (or equivalent ahead check)
    • if branch is ahead, either:
      • push after pre-push confirmation, or
      • record explicit user-approved deferral
    • do not begin the next slice with implicit unpushed commits.
    • sync main at two times:
      • after PR merge: fetch + checkout main + pull --ff-only
      • before starting the next slice: re-verify local main matches origin/main.
  9. Enforce PR conflict prevention + recovery:
    • before each push to an open PR branch: git fetch origin --prune and check branch vs origin/main
    • if branch is behind main, integrate first (rebase origin/main unless user requests merge)
    • resolve conflicts locally, rerun required verification, then push
    • when rebase rewrites history, use only --force-with-lease (never plain --force)
    • still show pre-push plan and wait for approval before push
    • if conflicts occur, record decisions in .slice_tmp/<slice_id>/pr_conflict_recovery.md
    • if PR is already merged/closed, start a new follow-up branch from updated main instead of appending unrelated commits to the closed branch.
  10. If wrong-branch edits are discovered, run patch-first recovery:
    • stop edits on wrong branch
    • create .slice_tmp/<slice_id>/wrong_branch_recovery.patch in the correct slice
    • export exact diff from wrong branch to that file
    • reapply from patch artifact only (no memory retype)
    • verify parity before commit (no missing/extra hunks)
    • use commit message suffix (recovered-from-wrong-branch)
    • report source branch, target branch, patch path, and verification method.

One-liners

  • Start (local only):
    • powershell ./tools/dev/start_slice_worktree.ps1 -Branch work/v5.5d2
  • Start after syncing from remote main explicitly:
    • git fetch origin --prune; git checkout main; git pull --ff-only origin main; powershell ./tools/dev/start_slice_worktree.ps1 -Branch work/v5.5d2
  • Start and push upstream (explicit only):
    • powershell ./tools/dev/start_slice_worktree.ps1 -Branch work/v5.5d2 -Push
  • List worktrees:
    • powershell ./tools/dev/list_worktrees.ps1
  • Cleanup worktree + local branch:
    • powershell ./tools/dev/remove_slice_worktree.ps1 -Branch work/v5.5d2 -DeleteBranch

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is physicslab_worktrees?

Perfect for Development Agents needing efficient Git worktree management and branch automation. Start and clean PhysicsLab slice branches safely using git worktrees. Use when asked to create/start a slice branch (for example V5.5d2), start a milestone branch, or create a new worktree.

How do I install physicslab_worktrees?

Run the command: npx killer-skills add AhmedAlnasser2000/Science-Lab/physicslab_worktrees. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for physicslab_worktrees?

Key use cases include: Automating new slice/milestone branch creation, Managing worktrees efficiently with safe defaults, Enforcing best practices for Git workflow.

Which IDEs are compatible with physicslab_worktrees?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for physicslab_worktrees?

Requires PowerShell execution capabilities. Git repository access needed. Limited to specific branch naming conventions (e.g., `work/vX.Yz`).

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add AhmedAlnasser2000/Science-Lab/physicslab_worktrees. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use physicslab_worktrees immediately in the current project.

Related Skills

Looking for an alternative to physicslab_worktrees or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
Design

linear

Logo of lobehub
lobehub

Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says linear, linear issue, link linear, (3) creating PRs that reference Linear issues. Provides

73.4k
0
Communication

testing

Logo of lobehub
lobehub

Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup

73.3k
0
Communication

chat-sdk

Logo of lobehub
lobehub

chat-sdk is a unified TypeScript SDK for building chat bots across multiple platforms, providing a single interface for deploying bot logic.

73.0k
0
Communication