القائمة
Git worktree workflow. Commands, naming conventions, rules, and example workflow. Use when creating worktrees, switching branches, or starting parallel work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
End-to-end open-a-PR flow — run the staff-eng pre-flight self-review, commit and push via ship, then open the PR with a clear summary. Use when you say "open a PR", "create the PR", "ship this feature and open a PR", or "ready for review" and want the whole flow, not just a commit.
Batch-convert HEIC images (e.g., iPhone slide screenshots) to compressed JPGs that fit under Read tool size limits. Use when the user has HEIC files that need to be reviewed visually by Claude or batch-processed for any downstream tool.
Writing voice reference template for AI writing assistants. Captures authentic communication style patterns for code reviews, Slack messages, and other written communication.
Anti-sycophancy skill
Use before opening a PR, requesting reviews, marking a draft ready, or pushing a substantive code change to a feature branch — the author's own staff-engineer self-review gate. Triggers on "open a PR", "create the PR", "ready for review", "request reviews", "mark ready", "un-draft", "ship it", "I'm done", "ready to merge", "push this feature".
Recall full context from a past Claude session. Use when the user needs detailed context from previous work — architecture decisions, implementation approaches, debugging sessions, or conversation threads.
| name | worktree-workflow |
| description | Git worktree workflow. Commands, naming conventions, rules, and example workflow. Use when creating worktrees, switching branches, or starting parallel work. |
RULE: ALWAYS use git worktrees instead of checking out branches in the main working directory.
| Trigger | Action |
|---|---|
| Starting new feature/bugfix/task | Create worktree |
| Checking out PR branch for review | Create worktree |
| Working on branch other than current | Create worktree |
| User wants parallel work on multiple tasks | Create worktree per task |
# List existing worktrees (check first to avoid conflicts)
git worktree list
# Create worktree for NEW branch
git worktree add -b <branch-name> ../<repo>-<branch-name>
# Create worktree for EXISTING branch
git worktree add ../<repo>-<branch-name> <branch-name>
# Remove worktree when done
git worktree remove ../<repo>-<branch-name>
# Clean up stale references
git worktree prune
Worktrees are sibling directories to the repository:
/projects/
├── my-app/ # Main repo (stays on default branch)
├── my-app-feat-add-export/ # Worktree for feature work
├── other-repo/ # Main repo
├── other-repo-fix-button/ # Worktree for fix
# 1. From main repo, create worktree for a branch
cd my-app
git worktree add -b feat/add-export ../my-app-feat-add-export
# 2. Work in worktree
cd ../my-app-feat-add-export
# ... make changes ...
# 3. Commit and push (no permission needed in worktrees)
git add .
git commit -m "feat(exports): add CSV export"
git push -u origin feat/add-export
# 4. When merged, clean up
cd ../my-app
git worktree remove ../my-app-feat-add-export