From c6c6e75af670d8429fbf665d201aabd78340c580 Mon Sep 17 00:00:00 2001 From: Jason Walker <913443@dadeschools.net> Date: Thu, 2 Jul 2026 05:38:29 -0400 Subject: [PATCH] chore: remove deprecated recover-dirty-worktree.md (#46) --- .../templates/recover-dirty-worktree.md | 31 ------------------- 1 file changed, 31 deletions(-) delete mode 100644 skills/llm-project-workflow/templates/recover-dirty-worktree.md diff --git a/skills/llm-project-workflow/templates/recover-dirty-worktree.md b/skills/llm-project-workflow/templates/recover-dirty-worktree.md deleted file mode 100644 index d8d54b3..0000000 --- a/skills/llm-project-workflow/templates/recover-dirty-worktree.md +++ /dev/null @@ -1,31 +0,0 @@ -# Recover Dirty Worktree Prompt - -You are recovering repository state in ``. - -Rules: - -- Do not reset, delete, clean, or overwrite work unless explicitly instructed. -- Do not edit another issue's worktree unless assigned to that issue. -- Preserve ambiguous work before any destructive operation. - -Workflow: - -1. Run `git status --short --branch`. -2. Identify whether dirty files belong to the current issue, another issue, or - unknown work. -3. If dirty work belongs to another issue, leave it alone and use a separate - worktree for the current task. -4. If an unauthorized untracked file was created, stop and report its exact path. -5. Remove unauthorized files only when explicitly instructed. -6. If local `` is ahead of `/`, stop and - report both commit hashes. -7. If cleanup is requested, verify the branch is merged or explicitly abandoned - before deleting any branch or worktree. - -Report: - -- current branch -- dirty files -- ownership assessment -- actions taken -- remaining blockers