@damper/cli 0.6.7 → 0.6.8
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.
|
@@ -128,7 +128,6 @@ This project uses Damper MCP for task tracking. **You MUST follow this workflow.
|
|
|
128
128
|
- \`publish_changelog\` - Publish with optional email notifications and Twitter posting
|
|
129
129
|
|
|
130
130
|
### At Session End (MANDATORY)
|
|
131
|
-
- ALWAYS call \`add_note\` with session summary before stopping
|
|
132
131
|
- ALWAYS call \`complete_task\` (if done) or \`abandon_task\` (if stopping early)
|
|
133
132
|
- NEVER leave a started task without completing or abandoning it
|
|
134
133
|
- If you learned something about the codebase, consider updating project context
|
|
@@ -25,9 +25,9 @@ ${planSection}
|
|
|
25
25
|
|
|
26
26
|
**Your responsibilities (via Damper MCP):**
|
|
27
27
|
1. Use \`add_commit\` after each git commit
|
|
28
|
-
2. Use \`add_note\` for
|
|
29
|
-
3. When done: call \`complete_task\` with summary
|
|
30
|
-
4. If stopping early: call \`abandon_task\` with
|
|
28
|
+
2. Use \`add_note\` ONLY for non-obvious approach decisions (e.g. "Decision: chose X because Y")
|
|
29
|
+
3. When done: call \`complete_task\` with a one-line summary
|
|
30
|
+
4. If stopping early: call \`abandon_task\` with what remains and blockers
|
|
31
31
|
|
|
32
32
|
The CLI just bootstrapped this environment - YOU handle the task lifecycle.
|
|
33
33
|
`.trim();
|
|
@@ -66,7 +66,7 @@ export function generateTaskContext(options) {
|
|
|
66
66
|
}
|
|
67
67
|
// Previous Session Notes
|
|
68
68
|
if (task.agentNotes) {
|
|
69
|
-
lines.push('## Previous
|
|
69
|
+
lines.push('## Previous Notes');
|
|
70
70
|
lines.push('');
|
|
71
71
|
lines.push(task.agentNotes);
|
|
72
72
|
lines.push('');
|