elliot-stack 1.0.29 → 1.0.33

package/skills/estack-repo-search/SKILL.md

@@ -1,68 +1,68 @@
----
-name: estack-repo-search
-version: 1.0.2
-description: >-
-  (repo-search) Clone and search external GitHub repositories to answer questions about their
-  code. Use this skill whenever the user references a repo you don't have local
-  context for, asks about code in an external project, wants to compare
-  implementations across repos, or needs information from a codebase that isn't
-  in the current working directory. Also use when the user says things like
-  "check how X does it", "look at the source for Y", "search that repo",
-  "clone it and find...", or references a GitHub URL. If you're unsure whether
-  you have enough context about an external codebase to answer accurately,
-  use this skill to clone it and look.
----
-
-# Repo Search
-
-Search external repositories by cloning them into a persistent sandbox and exploring with subagents.
-
-## Available repos
-
-```!
-mkdir -p ~/repo-search-storage
-echo "=== Repo Sandbox: ~/repo-search-storage ==="
-echo ""
-found=0
-for dir in ~/repo-search-storage/*/; do
-  [ -d "$dir/.git" ] || continue
-  found=1
-  name=$(basename "$dir")
-  url=$(cd "$dir" && git remote get-url origin 2>/dev/null || echo "(no remote)")
-  echo "- $name  →  $url"
-  echo "  Updating..."
-  (cd "$dir" && git pull --ff-only 2>&1) | sed 's/^/  /'
-  echo ""
-done
-if [ "$found" -eq 0 ]; then
-  echo "(no repos cached yet)"
-fi
-```
-
-Present the user with the repos listed above and offer to search any of them or clone a new one.
-
-## Finding the correct repo
-
-Before cloning, you must have the exact GitHub URL. Follow these rules:
-
-- **If the user gave a full GitHub URL** (e.g. `https://github.com/org/repo`), use it directly.
-- **If the user gave only a name** (e.g. "openclaw", "langchain"), use WebSearch to find the correct GitHub repository URL first. Never guess a repo URL — confirm it via search.
-- **Always verify** the search result matches what the user is asking about before cloning. It doesn't hurt to confirm with the user — "I found X repo, is that the one you meant?" — before spending time cloning. Wrong repo = wasted time and misleading answers.
-
-## Cloning
-
-Once you have a confirmed URL, shallow clone into the sandbox:
-
-```bash
-git clone --depth 1 <repo-url> ~/repo-search-storage/<repo-name>
-```
-
-## Searching
-
-To explore a repo, spawn one or more **Haiku** subagents using the Agent tool with `model: "haiku"` and `subagent_type: "Explore"`. In the prompt, always include the **full absolute path** to the cloned repo (e.g. `C:/Users/2supe/repo-search-storage/gstack`) and tell the subagent to search within that directory. Without this, the subagent won't know where to look.
-
-If the question spans multiple areas of the repo, spawn multiple subagents in parallel — each focused on a different aspect — to get answers faster.
-
+---
+name: estack-repo-search
+version: 1.0.2
+description: >-
+  (repo-search) Clone and search external GitHub repositories to answer questions about their
+  code. Use this skill whenever the user references a repo you don't have local
+  context for, asks about code in an external project, wants to compare
+  implementations across repos, or needs information from a codebase that isn't
+  in the current working directory. Also use when the user says things like
+  "check how X does it", "look at the source for Y", "search that repo",
+  "clone it and find...", or references a GitHub URL. If you're unsure whether
+  you have enough context about an external codebase to answer accurately,
+  use this skill to clone it and look.
+---
+
+# Repo Search
+
+Search external repositories by cloning them into a persistent sandbox and exploring with subagents.
+
+## Available repos
+
+```!
+mkdir -p ~/repo-search-storage
+echo "=== Repo Sandbox: ~/repo-search-storage ==="
+echo ""
+found=0
+for dir in ~/repo-search-storage/*/; do
+  [ -d "$dir/.git" ] || continue
+  found=1
+  name=$(basename "$dir")
+  url=$(cd "$dir" && git remote get-url origin 2>/dev/null || echo "(no remote)")
+  echo "- $name  →  $url"
+  echo "  Updating..."
+  (cd "$dir" && git pull --ff-only 2>&1) | sed 's/^/  /'
+  echo ""
+done
+if [ "$found" -eq 0 ]; then
+  echo "(no repos cached yet)"
+fi
+```
+
+Present the user with the repos listed above and offer to search any of them or clone a new one.
+
+## Finding the correct repo
+
+Before cloning, you must have the exact GitHub URL. Follow these rules:
+
+- **If the user gave a full GitHub URL** (e.g. `https://github.com/org/repo`), use it directly.
+- **If the user gave only a name** (e.g. "openclaw", "langchain"), use WebSearch to find the correct GitHub repository URL first. Never guess a repo URL — confirm it via search.
+- **Always verify** the search result matches what the user is asking about before cloning. It doesn't hurt to confirm with the user — "I found X repo, is that the one you meant?" — before spending time cloning. Wrong repo = wasted time and misleading answers.
+
+## Cloning
+
+Once you have a confirmed URL, shallow clone into the sandbox:
+
+```bash
+git clone --depth 1 <repo-url> ~/repo-search-storage/<repo-name>
+```
+
+## Searching
+
+To explore a repo, spawn one or more **Haiku** subagents using the Agent tool with `model: "haiku"` and `subagent_type: "Explore"`. In the prompt, always include the **full absolute path** to the cloned repo (e.g. `C:/Users/2supe/repo-search-storage/gstack`) and tell the subagent to search within that directory. Without this, the subagent won't know where to look.
+
+If the question spans multiple areas of the repo, spawn multiple subagents in parallel — each focused on a different aspect — to get answers faster.
+
 ---
 
 ## Skill Feedback

package/skills/estack-vscode-file-recovery/SKILL.md

@@ -0,0 +1,188 @@
+---
+name: estack-vscode-file-recovery
+version: 1.2.0
+description: >
+  (vscode-file-recovery) Recover files that were permanently deleted (via rm, bash delete, or any method that bypasses the Recycle Bin) using VS Code's or Cursor's Local History snapshots, or from Claude session transcripts.
+  Use this skill immediately whenever: a file was deleted and git can't recover it (untracked or not committed), the user says "get it back", "restore that file", "I lost that file", "can you undo that delete", or any variation of wanting a deleted file recovered. Also use proactively after any rm or bash delete of files that weren't committed to git.
+  VS Code and Cursor silently save a snapshot every time you open or edit a file in the editor — this is often the only recovery path when git and Recycle Bin both fail.
+---
+
+# VS Code / Cursor File Recovery
+
+When a file is deleted outside of git (with `rm`, bash, or any method that bypasses the Recycle Bin), this skill recovers it from editor Local History or Claude session transcripts.
+
+## Recovery Sources — Try in Order
+
+1. **Editor Local History** (VS Code or Cursor) — covered below
+2. **Claude session transcript** — if Claude read the file in a prior session, its content may be in the JSONL. Use `/read-transcript` to search session history.
+3. **Git** — only if the file was ever committed
+4. **Cloud sync** (OneDrive, Dropbox) — check the cloud recycle bin / version history
+
+---
+
+## How Editor Local History Works
+
+VS Code and Cursor automatically save timestamped snapshots of every file opened in the editor. These live at:
+
+```
+VS Code  (Windows): C:\Users\[username]\AppData\Roaming\Code\User\History\
+Cursor   (Windows): C:\Users\[username]\AppData\Roaming\Cursor\User\History\
+VS Code  (Mac):     ~/Library/Application Support/Code/User/History/
+Cursor   (Mac):     ~/Library/Application Support/Cursor/User/History/
+VS Code  (Linux):   ~/.config/Code/User/History/
+Cursor   (Linux):   ~/.config/Cursor/User/History/
+```
+
+Each file gets a hash-named folder containing:
+- `entries.json` — maps the original file path to snapshot IDs and timestamps
+- `[id].[ext]` — the actual snapshot content (e.g., `dtgz.md`, `F9gm.txt`)
+
+**Critical limitation:** VS Code only snapshots files that were actually *opened as a tab in the editor*. Files visible only in the sidebar Explorer are not captured.
+
+---
+
+## Recovery Steps
+
+### Step 1: Identify what to search for
+
+Collect from the user (or from the deletion event):
+- The filename (e.g., `Untitled-1.md`)
+- The full path if known (e.g., `C:\Users\2supe\All Coding\akiflow-mcp\Untitled-1.md`)
+- Any partial path segments (folder name, project name)
+
+### Step 2: Search editor history for the file
+
+Search `entries.json` files in both VS Code and Cursor History directories.
+
+**Windows (PowerShell) — searches both editors:**
+```powershell
+@("Code", "Cursor") | ForEach-Object {
+  $histPath = "$env:APPDATA\$_\User\History"
+  if (Test-Path $histPath) {
+    Get-ChildItem $histPath -Recurse |
+      Where-Object { $_.Name -eq "entries.json" } |
+      ForEach-Object {
+        $content = Get-Content $_.FullName -Raw -ErrorAction SilentlyContinue
+        if ($content -like "*FILENAME_OR_PATH_PATTERN*") {
+          $_.FullName
+          $content
+        }
+      }
+  }
+}
+```
+
+Replace `FILENAME_OR_PATH_PATTERN` with the filename or path fragment. **Use `-like "*filename*"` rather than `-match "filename"` to avoid regex metacharacter issues** (`.`, `(`, `)`, `+` in filenames break `-match`).
+
+If matching a full path, note that editors URL-encode it in `entries.json`: drive colons become `%3A`, backslashes become `/`, and spaces become `%20`. Example: `C:\Users\2supe\My App (v2).md` → `file:///c%3A/Users/2supe/My%20App%20%28v2%29.md`. **Searching by filename alone is simpler and usually sufficient.**
+
+**Mac (bash) — searches both editors:**
+```bash
+for app in "Code" "Cursor"; do
+  grep -rl "FILENAME_OR_PATH_PATTERN" "$HOME/Library/Application Support/$app/User/History/" 2>/dev/null
+done
+```
+
+### Step 3: Read the entries.json to find the latest snapshot
+
+The `entries.json` looks like:
+```json
+{
+  "version": 1,
+  "resource": "file:///c%3A/Users/2supe/path/to/Untitled-1.md",
+  "entries": [
+    {"id": "F9gm.md", "source": "Workspace Edit", "timestamp": 1776196985353},
+    {"id": "U4ha.md", "source": "Workspace Edit", "timestamp": 1776197058059},
+    {"id": "dtgz.md", "source": "Workspace Edit", "timestamp": 1776197128275}
+  ]
+}
+```
+
+The **last entry** in the array is the most recent snapshot. Take its `id` field.
+
+### Step 4: Read the snapshot content
+
+```powershell
+Get-Content "C:\Users\[username]\AppData\Roaming\Code\User\History\[hash-folder]\[id]"
+```
+
+Or use the Read tool with the full path.
+
+### Step 5: Restore the file
+
+Write the content back to the original location using the Write tool.
+
+---
+
+## When Editor History Won't Help
+
+- **File was never opened as an editor tab** — files only visible in the sidebar Explorer are not snapshotted.
+- **History was cleared** — default retention is 30 days / 50 entries per file.
+
+If editor history doesn't have the file, fall back to:
+1. **`/read-transcript`** — if Claude read the file in a prior session, the content is in the session JSONL. Use `--mode search --query "filename"` to find it. Note: you need to point it at the right project's sessions — if the file lived in a different project folder, search that project's transcript directory instead.
+2. **Windows Shadow Copies** (last resort, requires admin) — Windows VSS may have a snapshot of the volume. Check if any exist first:
+   ```powershell
+   vssadmin list shadows
+   ```
+   If a shadow copy exists, mount it and browse (**requires an elevated/admin shell**; the trailing backslash on the device path is required or `mklink` fails silently):
+   ```powershell
+   cmd /c mklink /d C:\shadow \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3\
+   ```
+   Replace the device path with the one from `vssadmin list shadows`. Browse `C:\shadow\` like a normal drive to find and copy the file back. Clean up after: `cmd /c rmdir C:\shadow`.
+3. **File recovery software** (Recuva on Windows) — only works if the disk blocks haven't been overwritten yet.
+
+---
+
+## Example
+
+**Scenario:** `rm` deleted `Untitled-1.md` which was untracked by git.
+
+```powershell
+# Search
+Get-ChildItem "$env:APPDATA\Code\User\History" -Recurse |
+  Where-Object { $_.Name -eq "entries.json" } |
+  ForEach-Object {
+    $content = Get-Content $_.FullName -Raw -ErrorAction SilentlyContinue
+    if ($content -like "*Untitled-1*") { $_.FullName; $content }
+  }
+
+# Result shows: C:\...\History\-6e228c75\entries.json
+# entries.json has latest id: "dtgz.md"
+
+# Read snapshot
+Get-Content "C:\Users\2supe\AppData\Roaming\Code\User\History\-6e228c75\dtgz.md"
+
+# Restore
+# (Use Write tool to recreate the file at original path)
+```
+---
+
+## Skill Feedback
+
+If the user shares feedback about this skill — a bug, something confusing, a missing feature, or a suggestion — ask them to describe it in a bit more detail (what they expected, what happened, and any relevant context). Then file the issue using whichever method is available:
+
+**If `gh` is installed** (`gh --version` succeeds), create the issue directly:
+
+```bash
+gh issue create \
+  --repo ElliotDrel/e-stack \
+  --title "estack-vscode-file-recovery: <concise summary>" \
+  --body "<description from user feedback — expected vs. actual behavior and context>"
+```
+
+**If `gh` is not installed**, build a pre-filled URL:
+
+```bash
+python3 -c "
+import urllib.parse
+title = 'estack-vscode-file-recovery: <concise summary>'
+body = '<description from user feedback — expected vs. actual behavior and context>'
+base = 'https://github.com/ElliotDrel/e-stack/issues/new'
+print(base + '?title=' + urllib.parse.quote(title) + '&body=' + urllib.parse.quote(body))
+"
+```
+
+Share the printed URL with the user and offer to open it in their browser.
+
+They can also click it directly, review the pre-filled title and body, and click **Submit new issue**.