shoko/kugetsu
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

[Phase 6] Add dry-run support to cmd_continue #249

New Issue
Open
opened 2026-04-08 06:34:39 +02:00 by shoko · 0 comments
shoko commented 2026-04-08 06:34:39 +02:00
Owner
Copy Link

Problem

Testing the queue-daemon is difficult because fork_agent() spawns opencode which consumes 340MB-1GB per session.

Solution

Add dry-run mode to cmd_continue:

  • Check for KUGEETSU_DRY_RUN=1 env var OR --dry-run flag
  • If either is provided, exit immediately with code 0 before ANY file operations
  • Output: "Dry run mode - no files modified"

Implementation in cmd_continue:

if [ "${KUGEETSU_DRY_RUN:-}" = "1" ] || [ "${1:-}" = "--dry-run" ] || [ "${2:-}" = "--dry-run" ]; then
    echo "Dry run mode - no files modified"
    return 0
fi

Status

BLOCKED - Depends on Phase 5 (uses exit code 0 for dry-run)

Files

  • skills/kugetsu/scripts/kugetsu-session.sh

Related Issues

Parent: #235
Blocked by: #240 (Phase 5)

## Problem Testing the queue-daemon is difficult because fork_agent() spawns opencode which consumes 340MB-1GB per session. ## Solution Add dry-run mode to cmd_continue: - Check for KUGEETSU_DRY_RUN=1 env var OR --dry-run flag - If either is provided, exit immediately with code 0 before ANY file operations - Output: "Dry run mode - no files modified" Implementation in cmd_continue: ```bash if [ "${KUGEETSU_DRY_RUN:-}" = "1" ] || [ "${1:-}" = "--dry-run" ] || [ "${2:-}" = "--dry-run" ]; then echo "Dry run mode - no files modified" return 0 fi ``` ## Status **BLOCKED** - Depends on Phase 5 (uses exit code 0 for dry-run) ## Files - skills/kugetsu/scripts/kugetsu-session.sh ## Related Issues Parent: #235 Blocked by: #240 (Phase 5)
shoko added the blocked label 2026-04-08 06:38:30 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.2.x-only
Available only in 0.2.x, not backportable
 0.3.x-only
Available only in 0.3.x, not backportable
 backport
Backport compatible - can merge to 0.1.x
 blocked
Issue needs clarification/discussion before it can be worked on
 bug
Bug report
 critical
Critical - blocking parallel work
 feature
New feature
 foundation
Foundation work for 0.2.x
 high
High priority - workflow improvements
 meta
Meta issue tracking multiple issues
 need-review
PR needs review before merge
 parallelization
Issues related to parallelization
 ready
Issue is clear and ready to be implemented/delegated
 ready-to-merge
PR approved and ready to merge
 task-delegation
Issues related to task-delegation
No Label blocked
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
shoko
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: shoko/kugetsu#249
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?