Use when the user asks about dsh-tui itself (usage, shortcuts, config, themes, migration, VS Code). Load before answering; skip for normal coding tasks.
Review or de-slop concrete changes in ccch1mneyyy/dsh-TUI at maintainer level: PR numbers or URLs, branches, commit ranges, patch files, staged or unstaged worktrees, and scoped repository-hygiene requests. Use for evidence-first correctness, contract,…
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.
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.
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.
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.
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.
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.