@xelth/eck-snapshot 4.2.3 → 4.3.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.


This version of @xelth/eck-snapshot might be problematic. Click here for more details.

Files changed (2) hide show
  1. package/README.md +63 -3
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -32,9 +32,29 @@ npm install -g @xelth/eck-snapshot
32
32
 
33
33
  Once installed, you can run the tool using the `eck-snapshot` command from any directory.
34
34
 
35
- ## A Step-by-Step Guide to Using eckSnapshot
35
+ ## Workflow Options
36
36
 
37
- Here’s the most common workflow, from creating a full snapshot to focusing on specific features.
37
+ ### Option 1: Skeleton Workflow (Recommended for Large Projects)
38
+
39
+ The skeleton workflow is optimized for web-based LLMs (Gemini, ChatGPT) with large context windows. It uses a three-step approach:
40
+
41
+ 1. **Initial Context (Maximum Compression):** Create a lightweight map of your entire project where function/method bodies are hidden, showing only signatures and structure.
42
+ ```bash
43
+ eck-snapshot --skeleton
44
+ ```
45
+ This generates `.eck/snapshots/<name>_sk.md` - a compressed overview that fits even large monoliths into the context window.
46
+
47
+ 2. **Lazy Loading (On-Demand Details):** When the AI needs implementation details, use the `show` command to display specific files:
48
+ ```bash
49
+ eck-snapshot show src/auth.js src/utils/hash.js
50
+ ```
51
+ Copy-paste the output back to your AI chat.
52
+
53
+ 3. **Incremental Updates:** See the dedicated section below for details on the `update` command.
54
+
55
+ ### Option 2: Full Snapshot Workflow
56
+
57
+ Here's the traditional workflow for creating complete snapshots and focusing on specific features.
38
58
 
39
59
  #### Step 1: Create a Full Project Snapshot
40
60
 
@@ -106,16 +126,56 @@ A faster, non-AI method to reduce snapshot size. This command keeps only the top
106
126
  > eck-snapshot --max-lines-per-file 200
107
127
  > ```
108
128
 
129
+ ## Incremental Updates: The `update` Command
130
+
131
+ The `update` command is a powerful feature that creates **delta snapshots** containing only the files that changed since your last full snapshot. This is essential for maintaining AI context efficiently during active development.
132
+
133
+ ### How It Works
134
+
135
+ 1. **Anchor Point:** When you create a full snapshot (with `eck-snapshot` or `eck-snapshot --skeleton`), the current git commit hash is saved as an "anchor" in `.eck/.snapshot-anchor`.
136
+
137
+ 2. **Change Detection:** The `update` command compares your current working directory against this anchor to identify all modified, added, or deleted files.
138
+
139
+ 3. **Delta Generation:** It creates a new snapshot file containing:
140
+ - Only the changed files (with full content)
141
+ - A git diff showing all changes for context
142
+ - Clear instructions for the AI to merge these changes with the base snapshot
143
+
144
+ ### Usage
145
+
146
+ ```bash
147
+ eck-snapshot update
148
+ ```
149
+
150
+ This generates `.eck/snapshots/update_<timestamp>.md`.
151
+
152
+ ### When to Use
153
+
154
+ - **During active development:** After making changes based on AI suggestions, send an update instead of the entire codebase
155
+ - **Iterative workflows:** Keep the AI synchronized with your latest code without re-uploading everything
156
+ - **Large projects:** Especially valuable when the full snapshot is large - updates are typically much smaller
157
+
158
+ ### Important Notes
159
+
160
+ - You must create a full snapshot first before using `update`
161
+ - Each update is self-contained - send only the latest update to the AI, not all previous updates
162
+ - The AI is instructed to "merge" the update over the base snapshot mentally
163
+ - Works with both regular and skeleton snapshots
164
+
109
165
  ## Auxiliary Commands
110
166
 
111
167
  * `restore <snapshot_file>`: Recreates a project's file structure from a snapshot.
112
168
  * `generate-profile-guide`: Creates a guide for manual profile creation. Use this if `profile-detect` fails on very large projects, as it allows you to use an LLM with a larger context window (e.g., a web UI).
113
169
  * `detect`: Shows how `eckSnapshot` has identified your project type and what default file filters are being applied.
114
- * `ask-gpt` / `ask-claude`: Directly delegate a task to your configured AI coder agents from the command line.
170
+ * `ask-claude`: Directly delegate a task to your configured Claude Code CLI agent from the command line.
115
171
  * `setup-gemini`: A utility to automatically configure integration with the `gemini-cli`.
116
172
 
117
173
  For a full list of commands and options, run `eck-snapshot --help`.
118
174
 
175
+ ## Experimental Features
176
+
177
+ ⚠️ **juniorArchitect**: This feature is currently under development and not yet functional. It's intended to provide automated architectural analysis and suggestions. Contributions to complete this feature are welcome!
178
+
119
179
  ## License
120
180
 
121
181
  This project is licensed under the MIT License.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xelth/eck-snapshot",
3
- "version": "4.2.3",
3
+ "version": "4.3.1",
4
4
  "description": "A powerful CLI tool to create and restore single-file text snapshots of Git repositories and directories. Optimized for AI context and LLM workflows.",
5
5
  "main": "index.js",
6
6
  "type": "module",