issue-execute_skill

Overview

This skill automates serial execution of solutions from an issue queue, committing once per solution and supporting batch processing and execution control. It enforces project conventions by loading project tech stack, guidelines, and solution schema before running. Worktree support isolates work for parallel executors and provides resume and cleanup flows. The tool requires an explicit --queue parameter and provides dry-run, skip-test, and skip-build controls.

How this skill works

The skill fetches solutions one at a time with ccw issue next --queue <id>, executes each solution’s tasks sequentially (implement → test → verify), stages changes, and makes a single formatted git commit per solution. It auto-detects or creates a git worktree when requested to isolate execution, reports completion with ccw issue done, and repeats until the queue is empty. On completion it prompts the user to merge, open a PR, or keep the branch and cleans up the worktree accordingly.

When to use it

• Automating execution of a structured issue queue where each solution must be committed separately
• Parallelizing execution across isolated worktrees to avoid workspace conflicts
• Resuming interrupted executions by passing an existing worktree path
• Enforcing project-specific conventions by loading tech stack and guidelines before changes
• Previewing actions with --dry-run before making commits

Best practices

• Always pass --queue=<id>; the skill will not auto-select a queue for you
• Use --worktree new or a timestamped worktree for parallel executors to keep main repo clean
• Run from the repository root and use absolute paths for worktree creation to avoid path issues
• Prefer 'Create PR' for parallel executors to avoid merge races; merge only when main is clean
• Use --skip-tests or --skip-build only when you have a valid reason and include manual verification when skipping automated checks

Example use cases

• Process a backlog queue and commit each implemented solution with a clear commit message
• Run automated feature implementations across multiple isolated worktrees in parallel and open a PR per executor
• Resume a previously interrupted run by passing the existing worktree path to continue where it stopped
• Perform a dry run to preview all planned implement/test/commit steps without modifying files
• Execute bugfix strategy: reproduce, implement, run edge-case tests, commit, and report completion