@damper/cli 0.9.0 → 0.9.2

package/dist/services/claude.js

@@ -307,7 +307,18 @@ export async function postTaskFlow(options) {
                     console.log(pc.dim('Merging feature into main...'));
                     await execa('git', ['checkout', 'main'], { cwd: projectRoot, stdio: 'pipe' });
                     await execa('git', ['merge', currentBranch, '--no-edit'], { cwd: projectRoot, stdio: 'inherit' });
-                    console.log(pc.green('✓ Merged to main locally\n'));
+                    console.log(pc.green('✓ Merged to main locally'));
+                    const shouldPush = await confirm({
+                        message: 'Push main to origin?',
+                        default: false,
+                    });
+                    if (shouldPush) {
+                        await execa('git', ['push', 'origin', 'main'], { cwd: projectRoot, stdio: 'inherit' });
+                        console.log(pc.green('✓ Pushed main to origin\n'));
+                    }
+                    else {
+                        console.log(pc.dim('Skipped push. Run `git push origin main` when ready.\n'));
+                    }
                 }
             }
             catch (err) {

package/dist/templates/CLAUDE_APPEND.md.js

@@ -24,10 +24,11 @@ ${planSection}
 - \`.claude/settings.local.json\`
 
 **Your responsibilities (via Damper MCP):**
-1. Use \`add_commit\` after each git commit
-2. Use \`add_note\` ONLY for non-obvious approach decisions (e.g. "Decision: chose X because Y")
-3. When done: call \`complete_task\` with a one-line summary
-4. If stopping early: call \`abandon_task\` with what remains and blockers
+1. **Do NOT commit or complete tasks without explicit user confirmation** - Always ask the user before running \`git commit\` or calling \`complete_task\`
+2. Use \`add_commit\` after each git commit
+3. Use \`add_note\` ONLY for non-obvious approach decisions (e.g. "Decision: chose X because Y")
+4. When user confirms: call \`complete_task\` with a one-line summary
+5. If stopping early: call \`abandon_task\` with what remains and blockers
 
 The CLI just bootstrapped this environment - YOU handle the task lifecycle.
 `.trim();

package/dist/templates/TASK_CONTEXT.md.js

@@ -44,7 +44,8 @@ export function generateTaskContext(options) {
     lines.push('- Generated this TASK_CONTEXT.md from Damper API');
     lines.push('- Configured Damper MCP tools for task lifecycle');
     lines.push('');
-    lines.push('**Cleanup:** When done, call `complete_task` or `abandon_task`. The user will run');
+    lines.push('**Cleanup:** Ask the user for confirmation before committing or completing the task.');
+    lines.push('Once confirmed, call `complete_task` or `abandon_task`. The user will run');
     lines.push('`npx @damper/cli cleanup` to remove the worktree and branch - you don\'t need to');
     lines.push('provide manual cleanup instructions.');
     lines.push('');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@damper/cli",
-  "version": "0.9.0",
+  "version": "0.9.2",
   "description": "CLI tool for orchestrating Damper task workflows with Claude Code",
   "author": "Damper <hello@usedamper.com>",
   "repository": {