@xelth/eck-snapshot 6.0.1 → 6.0.2

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.
Files changed (4) hide show
  1. package/package.json +1 -1
  2. package/src/templates/opencode/coder.template.md +13 -10
  3. package/src/templates/opencode/junior-architect.template.md +14 -11
  4. package/src/utils/claudeMdGenerator.js +24 -12
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xelth/eck-snapshot",
3
- "version": "6.0.1",
3
+ "version": "6.0.2",
4
4
  "description": "A powerful CLI tool to create and restore single-file text snapshots of Git repositories. Optimized for AI context, LLM workflows, and multi-agent Swarm coordination.",
5
5
  "main": "index.js",
6
6
  "type": "module",
package/src/templates/opencode/coder.template.md CHANGED
@@ -6,17 +6,20 @@ You are an Expert Developer. The architecture is already decided. Your job is to
6
6
  ## DEFINITION OF DONE (CRITICAL)
7
7
  When task is complete, you must report back and sync context.
8
8
 
9
- **OPTION A: Using MCP Tool (Recommended)**
10
- Call the \`eck_finish_task\` tool. Pass your detailed markdown report into the \`status\` argument.
11
- - The tool will automatically write the report to \`AnswerToSA.md\`, commit, and generate a snapshot.
12
- - **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools (it will fail safety checks).
13
- - **WARNING: USE ONLY ONCE.** Do not use \`eck_finish_task\` for intermediate testing. It spams snapshot history.
9
+ **PRIMARY METHOD: Use `eck_finish_task` MCP tool.**
10
+ Pass your detailed markdown report into the `status` argument.
11
+ - The tool will automatically write the report, commit, and generate a snapshot.
12
+ - **DO NOT** manually write to `AnswerToSA.md` with your file editing tools.
13
+ - **WARNING: USE ONLY ONCE.** Do not use for intermediate testing.
14
14
 
15
- **OPTION B: Manual CLI (Fallback)**
16
- If the MCP tool is unavailable:
17
- 1. **READ** \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED by safety rules before overwriting).
18
- 2. **WRITE** your report to that file.
19
- 3. Run \`eck-snapshot update\` in terminal.
15
+ **FALLBACK METHOD (Only if MCP tool is missing):**
16
+ If `eck_finish_task` is NOT in your available tools, you MUST do the following:
17
+ 0. **WARN THE USER:** State clearly in your response: "⚠️ `eck-core` MCP server is not connected. Proceeding with manual fallback."
18
+ 1. **READ:** Read `.eck/lastsnapshot/AnswerToSA.md` using your `Read` tool (REQUIRED before overwriting).
19
+ 2. **WRITE:** Overwrite that file with your report.
20
+ 3. **COMMIT (CRITICAL):** Run `git add .` and `git commit -m "chore: task report"` in the terminal.
21
+ 4. **SNAPSHOT:** Run `eck-snapshot update` in the terminal.
22
+ *(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
20
23
 
21
24
  ## PROJECT CONTEXT (.eck DIRECTORY)
22
25
  The `.eck/` directory contains critical project documentation. **Before starting your task, you MUST:**
package/src/templates/opencode/junior-architect.template.md CHANGED
@@ -36,18 +36,21 @@ For bulk work where delegation saves YOUR expensive context window, YOU MUST del
36
36
  ## 4. DEFINITION OF DONE (CRITICAL)
37
37
  When you have completed your coding task and verified it works, you must report back and sync context.
38
38
 
39
- **OPTION A: Using MCP Tool (Recommended)**
40
- Call the \`eck_finish_task\` tool. Pass your detailed markdown report into the \`status\` argument.
41
- - The tool will automatically write the report to \`AnswerToSA.md\`, commit, and generate a snapshot.
42
- - **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools.
43
- - **WARNING: USE ONLY ONCE.** Do not use \`eck_finish_task\` for intermediate testing. It spams snapshot history.
39
+ **PRIMARY METHOD: Use `eck_finish_task` MCP tool.**
40
+ Pass your detailed markdown report into the `status` argument.
41
+ - The tool will automatically write the report, commit, and generate a snapshot.
42
+ - **DO NOT** manually write to `AnswerToSA.md` with your file editing tools.
43
+ - **WARNING: USE ONLY ONCE.** Do not use for intermediate testing.
44
44
 
45
- **OPTION B: Manual CLI (Fallback)**
46
- If the MCP tool is unavailable:
47
- 1. **READ** \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED by safety rules before overwriting).
48
- 2. **WRITE** your report to that file.
49
- 3. Run \`eck-snapshot update\` in terminal.
50
- 4. If you are entirely blocked, use the \`eck_fail_task\` tool.
45
+ **FALLBACK METHOD (Only if MCP tool is missing):**
46
+ If `eck_finish_task` is NOT in your available tools, you MUST do the following:
47
+ 0. **WARN THE USER:** State clearly in your response: "⚠️ `eck-core` MCP server is not connected. Proceeding with manual fallback."
48
+ 1. **READ:** Read `.eck/lastsnapshot/AnswerToSA.md` using your `Read` tool (REQUIRED before overwriting).
49
+ 2. **WRITE:** Overwrite that file with your report.
50
+ 3. **COMMIT (CRITICAL):** Run `git add .` and `git commit -m "chore: task report"` in the terminal.
51
+ 4. **SNAPSHOT:** Run `eck-snapshot update` in the terminal.
52
+ *(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
53
+ 5. If you are entirely blocked, use the `eck_fail_task` tool.
51
54
 
52
55
  ## 5. SWARM ERROR RECOVERY & THE RALPH LOOP
53
56
  **Core Directive:** You are "deterministically persistent". Failures are expected, giving up is not.
package/src/utils/claudeMdGenerator.js CHANGED
@@ -48,9 +48,18 @@ Your task is NOT complete until code works globally.
48
48
  2. **Finish & Report:** Use the \`eck_finish_task\` MCP tool.
49
49
  - Pass your full markdown report into the \`status\` argument.
50
50
  - The tool will automatically write the report to \`.eck/lastsnapshot/AnswerToSA.md\`, commit, and generate a snapshot.
51
- - **DO NOT** try to manually write to \`.eck/lastsnapshot/AnswerToSA.md\` with the \`Write\` tool (it will fail safety checks).
51
+ - **DO NOT** try to manually write to \`.eck/lastsnapshot/AnswerToSA.md\` with the \`Write\` tool.
52
52
  - **WARNING:** USE ONLY ONCE PER TASK. Do not use this tool or \`eck-snapshot update\` for intermediate testing.
53
53
 
54
+ **FALLBACK METHOD (Only if MCP tool is missing):**
55
+ If \`eck_finish_task\` is NOT in your available tools, you MUST do the following:
56
+ 0. **WARN THE USER:** State clearly in your response: "⚠️ \`eck-core\` MCP server is not connected. Proceeding with manual fallback."
57
+ 1. **READ:** Read \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED before overwriting).
58
+ 2. **WRITE:** Overwrite that file with your report.
59
+ 3. **COMMIT (CRITICAL):** Run \`git add .\` and \`git commit -m "chore: task report"\` in the terminal.
60
+ 4. **SNAPSHOT:** Run \`eck-snapshot update\` in the terminal.
61
+ *(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
62
+
54
63
  ## 5. SWARM ERROR RECOVERY & ARCHITECT HYPOTHESES
55
64
  1. **Runtime Check:** Always check the \`.eck/RUNTIME_STATE.md\` and running processes before coding.
56
65
  2. **Challenge the Architect:** If the Architect's hypothesis is not confirmed during verification, discard it and look for the real root cause in the runtime.
@@ -72,17 +81,20 @@ You are an Expert Developer. The architecture is already decided. Your job is to
72
81
  ## DEFINITION OF DONE (CRITICAL)
73
82
  When task is complete, you must report back and sync context.
74
83
 
75
- **OPTION A: Using MCP Tool (Recommended)**
76
- Call the \`eck_finish_task\` tool. Pass your detailed markdown report into the \`status\` argument.
77
- - The tool will automatically write the report to \`AnswerToSA.md\`, commit, and generate a snapshot.
78
- - **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools (it will fail safety checks).
79
- - **WARNING: USE ONLY ONCE.** Do not use \`eck_finish_task\` for intermediate testing.
80
-
81
- **OPTION B: Manual CLI (Fallback)**
82
- If the MCP tool is unavailable:
83
- 1. **READ** \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED by safety rules before overwriting).
84
- 2. **WRITE** your report to that file.
85
- 3. Run \`eck-snapshot update\` in terminal.
84
+ **PRIMARY METHOD: Use \`eck_finish_task\` MCP tool.**
85
+ Pass your detailed markdown report into the \`status\` argument.
86
+ - The tool will automatically write the report, commit, and generate a snapshot.
87
+ - **DO NOT** manually write to \`AnswerToSA.md\` with your file editing tools.
88
+ - **WARNING: USE ONLY ONCE.** Do not use for intermediate testing.
89
+
90
+ **FALLBACK METHOD (Only if MCP tool is missing):**
91
+ If \`eck_finish_task\` is NOT in your available tools, you MUST do the following:
92
+ 0. **WARN THE USER:** State clearly in your response: "⚠️ \`eck-core\` MCP server is not connected. Proceeding with manual fallback."
93
+ 1. **READ:** Read \`.eck/lastsnapshot/AnswerToSA.md\` using your \`Read\` tool (REQUIRED before overwriting).
94
+ 2. **WRITE:** Overwrite that file with your report.
95
+ 3. **COMMIT (CRITICAL):** Run \`git add .\` and \`git commit -m "chore: task report"\` in the terminal.
96
+ 4. **SNAPSHOT:** Run \`eck-snapshot update\` in the terminal.
97
+ *(Note: The snapshot compares against the git anchor. If you skip step 3, it will say "No changes detected").*
86
98
 
87
99
  ## PROJECT CONTEXT (.eck DIRECTORY)
88
100
  The \`.eck/\` directory contains critical project documentation. **Before starting your task, you MUST:**