In the DSH ecosystem, converting an Issue into a PR often lacks controllability and traceability for intermediate steps. dsh-issue2pr is a global workflow plugin designed to transform the Issue-to-PR process into a series of steps through a structured 11-stage pipeline, with each step having input contracts, failure signals, rollbackable artifacts, and independently reviewable artifacts.

The plugin is maintained by LONGSASASASASA and follows the MIT license. It aims to provide an auditable system rather than simple text generation.

Core Features

The plugin covers the entire process from Issue analysis to PR construction. Core capabilities include:

  • 11-stage end-to-end pipeline: covers Issue analysis → retrieval → code understanding → root-cause hypothesis → task planning → coding → patch pipeline → testing → review → PR construction.
  • Human review gates: four gates are set at P5 / P6 / P9 / P11, and each gate must be released by approve or returned by reject for rework.
  • Artifact evidence chain: each stage writes numbered artifacts to disk (for example, 01-issue-analysis.), supporting independent review and rejection for rework.
  • Rollback mechanism: the Patch Pipeline maintains a ledger and rolls back only changes introduced by the Agent, without touching the user’s original code.
  • Real tests: executes real test commands in a cloned repository and persists the full output for traceability.
  • Multi-agent and external delegation: P6 supports built-in Planner / Coder / Reviewer collaboration, or delegation to a DSH session, Claude Code CLI, or DSH native agents.
  • Workbench UI: provides project / run / artifacts / configuration / description views and a floating intelligent assistant.
  • Git hosting connections: supports GitHub / GitLab / Huawei Cloud CodeArts, with credentials shared globally.
  • Stage-specific configuration: each stage can independently configure prompt, model, timeout, and other parameters.
  • End-to-end observability: records LLM calls, Git operations, and test execution status via trace/events.l.

Installation and Enablement

The plugin runs with the DSH host. The installation command is as follows:

dsh plugin --profile web add dsh-issue2pr

Working Principles

The plugin controls the execution flow by configuring different modes:

Review Mode

Determines which stages pause and wait for human intervention:

  • every: every stage enters a review gate after completion.
  • key-only: review only at P5 / P6 / P9 / P11 (recommended).
  • auto: proceed fully automatically; delegated stages still require validation that artifacts are available.

P6 Execution Mode

Determines who executes code generation:

  • builtin: built-in multi-agent collaboration.
  • session: generates a task package and hands it to a DSH session for manual execution.
  • claude: delegates execution to Claude Code CLI.
  • dsh: hands execution over to native agents in the DSH host.

Typical Usage

1. Create a Project

In the DSH sidebar, click “Issue2PR”, go to the project page, and create a new project. The project name, slug, and repository URL are required. The trigger source can be an Issue link or a local requirements document path.

2. Configure the Connection

For private repositories, add credentials in “Git Hosting Connections” and test connectivity. For public repositories, you can directly use the GITHUB_TOKEN environment variable.

3. Start a Run

Paste an Issue link or select a local requirements document. The plugin will automatically shallow clone the repository and start progressing.

4. Run and Review

View stage progress on the run page. When a review gate is encountered, inspect the artifacts and decide whether to approve or reject them. For delegated stages, approval requires ensuring that the artifacts are available.

5. Obtain the PR Description

After P11 passes, open the 10-pr-description. file, which includes the background, root cause, changes, verification evidence, and risk notes. 11-eval-report. is the Gate six-item self-assessment.

Application Scenarios and Notes

  • Environment requirements: DSH host, where the plugin shares the web lifecycle, Node.js ≥ 18, and git.
  • Dependencies: requires @deepseek-ai/dsh-client-runtime, @deepseek-ai/dsh-client-locale, and @deepseek-ai/dsh-client-ui-settings with versions ≥ 0.1.0-rc.2.
  • Suitable scenarios: automated development workflows that require strict traceability, rollback safety, and auditability.