Open or update a pull request in this repository, including writing or rewriting its description. Use for every PR you create or edit here, and for /pr.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Ship the current change as a pull request a reviewer can understand from the description alone: why it exists, the shape of the implementation, and what was actually verified.
issue-link CI check fails one without it. Docs-only PRs and PRs a maintainer labels no-issue-needed are exempt (docs/contributing.md). Reuse the issue the work came from; when there is none, open a tracking issue first — title [功能]/[Bug] …, body with 目标, 范围, and 非目标 sections, as in #919 — and link it.type(scope): summary (conventional commits, as in #1110); the commit body is English too. Stage explicit paths only, leave lib/ and unrelated worktree changes out, and push a branch whose upstream is itself, never main. Reuse the PR already open for the branch (gh pr view) instead of opening a second one.docs/contributing.md requires for the changed area when it has not run yet..github/PULL_REQUEST_TEMPLATE.md, following the HTML comments in it and then deleting them:
diff for a changed shape and a full block for a new one. For a terminal-visible change include the real rendered screen as a text block, captured headlessly the way the scripts/verify-*.tsx regressions render (renderToScreen or an @xterm/headless terminal).gh pr create --body-file or gh pr edit --body-file, then confirm the rendered body with gh pr view. Report the PR URL, the linked issue, and the CI state.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Audit the repository or a broad subsystem for security, correctness, and maintainability risks. Use for audit requests or /audit; use review for a specific change and vuln-check for a security-only assessment.
The English summary is being prepared. Showing the original description.
Turn a reported defect into an actionable bug report or issue draft. Use when the user asks to capture or document a bug; a request to fix broken behavior should proceed to diagnosis and repair.
The English summary is being prepared. Showing the original description.
Use when the user asks about dsh-tui itself (usage, shortcuts, config, themes, migration, VS Code). Load before answering; skip for normal coding tasks.
The English summary is being prepared. Showing the original description.
Read and triage existing pull request review comments, or address them when requested. Use for PR comment requests or /pr-comments; use review to inspect code without existing reviewer feedback.
The English summary is being prepared. Showing the original description.
Guide a programming exercise using dsh-tui or a topic the user wants to learn. Use for practice and coaching requests, rather than requests to deliver a product change.
The English summary is being prepared. Showing the original description.
Draft user-facing release notes from a verified release range. Use for release-note or changelog requests and /release-notes; writing notes alone does not imply publishing a release.
The English summary is being prepared. Showing the original description.