@deepseek-harness-tui/dsh-tui 0.5.0

package/lib/types/utils/mentions.d.ts

@@ -0,0 +1,30 @@
+/**
+ * `@` file-mention parsing (issue #15).
+ *
+ * A mention is an `@` that starts a whitespace-delimited token (string start
+ * or after whitespace) — `hello@world` never triggers. The token body is
+ * either a run of non-whitespace characters (`@src/a.ts`) or a double-quoted
+ * path (`@"my dir/a.ts"`, for paths containing spaces).
+ */
+export interface MentionToken {
+    /** Start index of the `@` in the source text. */
+    start: number;
+    /** End index (exclusive) of the whole token, quote included. */
+    end: number;
+    /** The referenced path as typed (unquoted, no leading `@`). */
+    path: string;
+}
+/** Extract every `@` mention in `text` (typed order, duplicates kept out). */
+export declare function extractMentions(text: string): MentionToken[];
+/**
+ * The mention token the caret is currently editing, if any: an `@` token
+ * that starts at or before the caret with the caret inside it. Used by the
+ * prompt's completion trigger so `@` works mid-message, not only at the
+ * start of the input.
+ */
+export declare function mentionAtCaret(value: string, cursor: number): {
+    start: number;
+    end: number;
+    query: string;
+} | undefined;
+//# sourceMappingURL=mentions.d.ts.map

package/lib/types/utils/mentions.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"mentions.d.ts","sourceRoot":"","sources":["../../../src/utils/mentions.ts"],"names":[],"mappings":"AAAA;;;;;;;GAOG;AAEH,MAAM,WAAW,YAAY;IAC3B,iDAAiD;IACjD,KAAK,EAAE,MAAM,CAAA;IACb,gEAAgE;IAChE,GAAG,EAAE,MAAM,CAAA;IACX,+DAA+D;IAC/D,IAAI,EAAE,MAAM,CAAA;CACb;AAMD,8EAA8E;AAC9E,wBAAgB,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,YAAY,EAAE,CA8B5D;AAED;;;;;GAKG;AACH,wBAAgB,cAAc,CAC5B,KAAK,EAAE,MAAM,EACb,MAAM,EAAE,MAAM,GACb;IAAE,KAAK,EAAE,MAAM,CAAC;IAAC,GAAG,EAAE,MAAM,CAAC;IAAC,KAAK,EAAE,MAAM,CAAA;CAAE,GAAG,SAAS,CAe3D"}

package/lib/types/utils/mentions.js

@@ -0,0 +1,72 @@
+/**
+ * `@` file-mention parsing (issue #15).
+ *
+ * A mention is an `@` that starts a whitespace-delimited token (string start
+ * or after whitespace) — `hello@world` never triggers. The token body is
+ * either a run of non-whitespace characters (`@src/a.ts`) or a double-quoted
+ * path (`@"my dir/a.ts"`, for paths containing spaces).
+ */
+/** True when `ch` delimits a token (whitespace). */
+const isBoundary = (ch) => ch === undefined || /\s/.test(ch);
+/** Extract every `@` mention in `text` (typed order, duplicates kept out). */
+export function extractMentions(text) {
+    const tokens = [];
+    const seen = new Set();
+    let index = 0;
+    while (index < text.length) {
+        const at = text.indexOf('@', index);
+        if (at === -1)
+            break;
+        index = at + 1;
+        if (!isBoundary(text[at - 1]))
+            continue; // email-style `a@b`, mid-token
+        if (text[at + 1] === '"') {
+            const close = text.indexOf('"', at + 2);
+            if (close === -1)
+                continue; // unterminated quote — not a mention
+            const path = text.slice(at + 2, close);
+            if (path && !seen.has(path)) {
+                seen.add(path);
+                tokens.push({ start: at, end: close + 1, path });
+            }
+            index = close + 1;
+            continue;
+        }
+        let end = at + 1;
+        while (end < text.length && !isBoundary(text[end]))
+            end++;
+        const path = text.slice(at + 1, end);
+        // A bare `@` or another trigger char (`@@`) carries no path.
+        if (path && !path.startsWith('@') && !seen.has(path)) {
+            seen.add(path);
+            tokens.push({ start: at, end, path });
+        }
+    }
+    return tokens;
+}
+/**
+ * The mention token the caret is currently editing, if any: an `@` token
+ * that starts at or before the caret with the caret inside it. Used by the
+ * prompt's completion trigger so `@` works mid-message, not only at the
+ * start of the input.
+ */
+export function mentionAtCaret(value, cursor) {
+    // Token start: scan back from the caret to the previous boundary.
+    let start = cursor;
+    while (start > 0 && !isBoundary(value[start - 1]))
+        start--;
+    if (value[start] !== '@')
+        return undefined;
+    // Quoted form: the caret must sit before the closing quote.
+    if (value[start + 1] === '"') {
+        const close = value.indexOf('"', start + 2);
+        if (close !== -1 && cursor > close)
+            return undefined;
+        return { start, end: close === -1 ? value.length : close + 1, query: value.slice(start + 2, cursor) };
+    }
+    // Token end: first boundary at/after the caret.
+    let end = cursor;
+    while (end < value.length && !isBoundary(value[end]))
+        end++;
+    return { start, end, query: value.slice(start + 1, cursor) };
+}

package/lib/types/utils/narration.d.ts

@@ -0,0 +1,11 @@
+/**
+ * Strip the `⏵` self-narration line from assistant text. The
+ * dsh-working-activity narrate contract puts exactly one `⏵` line at the
+ * very top of a reply; the live working line already surfaces it, so
+ * showing it again in the transcript would double it. Only the FIRST line
+ * is checked — the contract allows one `⏵` line per reply.
+ * @param text - Assistant text to strip.
+ * @returns The text without its leading `⏵` narration line.
+ */
+export declare function stripNarration(text: string): string;
+//# sourceMappingURL=narration.d.ts.map

package/lib/types/utils/narration.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"narration.d.ts","sourceRoot":"","sources":["../../../src/utils/narration.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AACH,wBAAgB,cAAc,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAKnD"}

package/lib/types/utils/narration.js

@@ -0,0 +1,16 @@
+/**
+ * Strip the `⏵` self-narration line from assistant text. The
+ * dsh-working-activity narrate contract puts exactly one `⏵` line at the
+ * very top of a reply; the live working line already surfaces it, so
+ * showing it again in the transcript would double it. Only the FIRST line
+ * is checked — the contract allows one `⏵` line per reply.
+ * @param text - Assistant text to strip.
+ * @returns The text without its leading `⏵` narration line.
+ */
+export function stripNarration(text) {
+    const newline = text.indexOf('\n');
+    const firstLine = newline === -1 ? text : text.slice(0, newline);
+    if (!firstLine.trimStart().startsWith('⏵'))
+        return text;
+    return newline === -1 ? '' : text.slice(newline + 1).replace(/^\n+/, '');
+}

package/lib/types/utils/semver.d.ts

@@ -0,0 +1,9 @@
+/**
+ * Minimal semver `>=` comparison for the ported Ink core (ink/terminal.ts
+ * gates hyperlink support on TERM_PROGRAM_VERSION).
+ * @param a - First version string (optional `v` prefix and pre-release suffix tolerated).
+ * @param b - Second version string.
+ * @returns True when `a` is greater than or equal to `b`.
+ */
+export declare function gte(a: string, b: string): boolean;
+//# sourceMappingURL=semver.d.ts.map

package/lib/types/utils/semver.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"semver.d.ts","sourceRoot":"","sources":["../../../src/utils/semver.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AACH,wBAAgB,GAAG,CAAC,CAAC,EAAE,MAAM,EAAE,CAAC,EAAE,MAAM,GAAG,OAAO,CAOjD"}

package/lib/types/utils/semver.js

@@ -0,0 +1,24 @@
+/**
+ * Minimal semver `>=` comparison for the ported Ink core (ink/terminal.ts
+ * gates hyperlink support on TERM_PROGRAM_VERSION).
+ * @param a - First version string (optional `v` prefix and pre-release suffix tolerated).
+ * @param b - Second version string.
+ * @returns True when `a` is greater than or equal to `b`.
+ */
+export function gte(a, b) {
+    const pa = parts(a);
+    const pb = parts(b);
+    for (let i = 0; i < 3; i += 1) {
+        if (pa[i] !== pb[i])
+            return pa[i] > pb[i];
+    }
+    return true;
+}
+function parts(version) {
+    const [major = 0, minor = 0, patch = 0] = version
+        .replace(/^v/, '')
+        .split('-')[0]
+        .split('.')
+        .map(part => Number.parseInt(part, 10) || 0);
+    return [major, minor, patch];
+}

package/lib/types/utils/sliceAnsi.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Slice a string containing ANSI escape codes.
+ *
+ * Unlike the slice-ansi package, this properly handles OSC 8 hyperlink
+ * sequences because @alcalzone/ansi-tokenize tokenizes them correctly.
+ * @param str - The ANSI string to slice.
+ * @param start - Start offset in display cells.
+ * @param end - End offset in display cells; defaults to the end of `str`.
+ * @returns The sliced string with its ANSI styling preserved.
+ */
+export default function sliceAnsi(str: string, start: number, end?: number): string;
+//# sourceMappingURL=sliceAnsi.d.ts.map

package/lib/types/utils/sliceAnsi.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"sliceAnsi.d.ts","sourceRoot":"","sources":["../../../src/utils/sliceAnsi.ts"],"names":[],"mappings":"AAmBA;;;;;;;;;GASG;AACH,MAAM,CAAC,OAAO,UAAU,SAAS,CAC/B,GAAG,EAAE,MAAM,EACX,KAAK,EAAE,MAAM,EACb,GAAG,CAAC,EAAE,MAAM,GACX,MAAM,CA8DR"}

package/lib/types/utils/sliceAnsi.js

@@ -0,0 +1,79 @@
+import { ansiCodesToString, reduceAnsiCodes, tokenize, undoAnsiCodes, } from '@alcalzone/ansi-tokenize';
+import { stringWidth } from '../ink/stringWidth.js';
+// A code is an "end code" if its code equals its endCode (e.g., hyperlink close)
+function isEndCode(code) {
+    return code.code === code.endCode;
+}
+// Filter to only include "start codes" (not end codes)
+function filterStartCodes(codes) {
+    return codes.filter(c => !isEndCode(c));
+}
+/**
+ * Slice a string containing ANSI escape codes.
+ *
+ * Unlike the slice-ansi package, this properly handles OSC 8 hyperlink
+ * sequences because @alcalzone/ansi-tokenize tokenizes them correctly.
+ * @param str - The ANSI string to slice.
+ * @param start - Start offset in display cells.
+ * @param end - End offset in display cells; defaults to the end of `str`.
+ * @returns The sliced string with its ANSI styling preserved.
+ */
+export default function sliceAnsi(str, start, end) {
+    // Don't pass `end` to tokenize — it counts code units, not display cells,
+    // so it drops tokens early for text with zero-width combining marks.
+    const tokens = tokenize(str);
+    let activeCodes = [];
+    let position = 0;
+    let result = '';
+    let include = false;
+    for (const token of tokens) {
+        // Advance by display width, not code units. Combining marks (Devanagari
+        // matras, virama, diacritics) are width 0 — counting them via .length
+        // advanced position past `end` early and truncated the slice. Callers
+        // pass start/end in display cells (via stringWidth), so position must
+        // track the same units.
+        const width = token.type === 'ansi' || token.type === 'control' ? 0 : token.fullWidth ? 2 : stringWidth(token.value);
+        // Break AFTER trailing zero-width marks — a combining mark attaches to
+        // the preceding base char, so "भा" (भ + ा, 1 display cell) sliced at
+        // end=1 must include the ा. Breaking on position >= end BEFORE the
+        // zero-width check would drop it and render भ bare. ANSI codes are
+        // width 0 but must NOT be included past end (they open new style runs
+        // that leak into the undo sequence), so gate on char type too. The
+        // !include guard ensures empty slices (start===end) stay empty even
+        // when the string starts with a zero-width char (BOM, ZWJ).
+        if (end !== undefined && position >= end) {
+            if (token.type === 'ansi' || width > 0 || !include)
+                break;
+        }
+        if (token.type === 'ansi') {
+            activeCodes.push(token);
+            if (include) {
+                // Emit all ANSI codes during the slice
+                result += token.code;
+            }
+        }
+        else {
+            if (!include && position >= start) {
+                // Skip leading zero-width marks at the start boundary — they belong
+                // to the preceding base char in the left half. Without this, the
+                // mark appears in BOTH halves: left+right ≠ original. Only applies
+                // when start > 0 (otherwise there's no preceding char to own it).
+                if (start > 0 && width === 0)
+                    continue;
+                include = true;
+                // Reduce and filter to only active start codes
+                activeCodes = filterStartCodes(reduceAnsiCodes(activeCodes));
+                result = ansiCodesToString(activeCodes);
+            }
+            if (include) {
+                // Control codes carry `code` (not `value`); keep them byte-for-byte.
+                result += token.type === 'control' ? token.code : token.value;
+            }
+            position += width;
+        }
+    }
+    // Only undo start codes that are still active
+    const activeStartCodes = filterStartCodes(reduceAnsiCodes(activeCodes));
+    result += ansiCodesToString(undoAnsiCodes(activeStartCodes));
+    return result;
+}

package/lib/types/working-activity.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Re-export of the `dsh-working-activity` plugin under this package's own
+ * name, so the bundle patch layer can mount the working-activity row as
+ * `@deepseek-harness-tui/dsh-tui/working-activity` instead of the bare package name.
+ *
+ * The dsh Loader resolves row names from the *profile* directory
+ * (`~/.dsh/profiles/<name>/`): only the profile's direct dependencies are
+ * linked into its node_modules. npm's flat layout also hoists transitive
+ * dependencies there, but pnpm's isolated layout never does — so the bare
+ * `dsh-working-activity` name (a transitive dependency of @deepseek-harness-tui/dsh-tui) fails
+ * with ERR_MODULE_NOT_FOUND at boot and the loader disposes the whole app,
+ * exiting the TUI before any UI appears (issue #60). Mounting through this
+ * subpath keeps resolution anchored at @deepseek-harness-tui/dsh-tui itself — always a direct
+ * profile dependency — and from its real location `dsh-working-activity`
+ * resolves under every package-manager layout.
+ * @module @deepseek-harness-tui/dsh-tui/working-activity
+ */
+export * from 'dsh-working-activity';
+//# sourceMappingURL=working-activity.d.ts.map

package/lib/types/working-activity.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"working-activity.d.ts","sourceRoot":"","sources":["../../src/working-activity.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;GAgBG;AACH,cAAc,sBAAsB,CAAA"}

package/lib/types/working-activity.js

@@ -0,0 +1,18 @@
+/**
+ * Re-export of the `dsh-working-activity` plugin under this package's own
+ * name, so the bundle patch layer can mount the working-activity row as
+ * `@deepseek-harness-tui/dsh-tui/working-activity` instead of the bare package name.
+ *
+ * The dsh Loader resolves row names from the *profile* directory
+ * (`~/.dsh/profiles/<name>/`): only the profile's direct dependencies are
+ * linked into its node_modules. npm's flat layout also hoists transitive
+ * dependencies there, but pnpm's isolated layout never does — so the bare
+ * `dsh-working-activity` name (a transitive dependency of @deepseek-harness-tui/dsh-tui) fails
+ * with ERR_MODULE_NOT_FOUND at boot and the loader disposes the whole app,
+ * exiting the TUI before any UI appears (issue #60). Mounting through this
+ * subpath keeps resolution anchored at @deepseek-harness-tui/dsh-tui itself — always a direct
+ * profile dependency — and from its real location `dsh-working-activity`
+ * resolves under every package-manager layout.
+ * @module @deepseek-harness-tui/dsh-tui/working-activity
+ */
+export * from 'dsh-working-activity';

package/package.json

@@ -0,0 +1,141 @@
+{
+  "name": "@deepseek-harness-tui/dsh-tui",
+  "version": "0.5.0",
+  "description": "Claude Code style interactive TUI front door for DeepSeek Harness agents, built on the ported Ink core.",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ccch1mneyyy/dsh-TUI.git"
+  },
+  "bugs": {
+    "url": "https://github.com/ccch1mneyyy/dsh-TUI/issues"
+  },
+  "homepage": "https://github.com/ccch1mneyyy/dsh-TUI#readme",
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module",
+  "bin": {
+    "dsh-tui": "./bin/dsh-tui.js"
+  },
+  "main": "lib/types/index.js",
+  "types": "lib/types/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./lib/types/index.d.ts",
+      "import": "./lib/types/index.js"
+    },
+    "./working-activity": {
+      "types": "./lib/types/working-activity.d.ts",
+      "import": "./lib/types/working-activity.js"
+    },
+    "./invariant": {
+      "types": "./lib/types/invariant.d.ts",
+      "default": "./lib/invariant.js"
+    },
+    "./cordis.patch.yml": "./cordis.patch.yml",
+    "./package.json": "./package.json",
+    "./src/*": "./src/*"
+  },
+  "files": [
+    "bin",
+    "lib",
+    "cordis.patch.yml",
+    "cordis.yml",
+    "skills"
+  ],
+  "engines": {
+    "node": "^22.19 || >=24"
+  },
+  "peerDependencies": {
+    "@deepseek-ai/cordis": "^4.0.1",
+    "@deepseek-ai/dsh-invariants": "^0.1.0-rc.6"
+  },
+  "dependencies": {
+    "@alcalzone/ansi-tokenize": "^0.3.0",
+    "@deepseek-ai/dsh-agent": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-agent-instructions": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-agent-presets": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-agent-tool-presentation": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-commands": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-cordis-host-runner": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-llm": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-persona": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-session": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-skill": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-system-prompt": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-terminal": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-terminal-bash": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-tool-ask-user": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-tool-bash-persistent": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-tool-cordis": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-user-questions": "^0.1.0-rc.6",
+    "@deepseek-ai/schemastery": "^3.18.1",
+    "auto-bind": "^4.0.0 || ^5.0.0",
+    "bidi-js": "^1.0.0",
+    "chalk": "^5.0.0",
+    "cli-boxes": "^3.0.0 || ^4.0.0",
+    "cli-highlight": "^2.1.11",
+    "code-excerpt": "^3.0.0 || ^4.0.0",
+    "dsh-working-activity": "^0.2.2",
+    "emoji-regex": "^10.0.0",
+    "figures": "^6.1.0",
+    "get-east-asian-width": "^1.0.0",
+    "highlight.js": "^11.11.1",
+    "indent-string": "^5.0.0",
+    "lodash-es": "^4.17.0",
+    "marked": "^18.0.7",
+    "react": "^19.2.0",
+    "react-reconciler": "^0.33.0",
+    "semver": "^7.0.0",
+    "signal-exit": "^4.0.0",
+    "stack-utils": "^2.0.0",
+    "strip-ansi": "^7.0.0",
+    "supports-hyperlinks": "^3.0.0",
+    "type-fest": "^4.0.0",
+    "usehooks-ts": "^3.1.0",
+    "wrap-ansi": "^8.0.0 || ^9.0.0"
+  },
+  "devDependencies": {
+    "@deepseek-ai/cordis": "^4.0.1",
+    "@deepseek-ai/cordis-plugin-include": "^1.0.6",
+    "@deepseek-ai/cordis-plugin-loader": "^1.0.2",
+    "@deepseek-ai/dsh-atomic-write": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-attachment": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-brand": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-code-runtime": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-fs": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-home-paths": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-invariants": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-session-persistence-jsonl": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-session-persistence-sqlite": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-sandbox": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-sandbox-policy": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-scope": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-session-persistence": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-settings": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-subprocess": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-timeout": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-tools": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-typert-protocol": "^0.1.0-rc.6",
+    "@deepseek-ai/dsh-user-approval": "^0.1.0-rc.6",
+    "@types/lodash-es": "^4.17.0",
+    "@types/node": "^22.0.0",
+    "@types/react": "^19.0.0",
+    "@types/react-reconciler": "^0.33.0",
+    "@types/semver": "^7.0.0",
+    "@xterm/headless": "^6.0.0",
+    "tsx": "^4.0.0",
+    "typescript": "^6.0.3"
+  },
+  "dsh": {
+    "bundle": {
+      "patch": "./cordis.patch.yml"
+    }
+  },
+  "scripts": {
+    "build": "tsc -p tsconfig.json",
+    "tui": "node --import tsx/esm scripts/run.ts",
+    "smoke": "node --import tsx/esm scripts/smoke.tsx"
+  }
+}

package/skills/audit/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: audit
+description: Use when asked to audit a codebase, or when the /audit command runs — find security, correctness, and quality issues across a project and report them organized by severity.
+---
+
+# Code Audit
+
+Audit the current project for security, correctness, and quality issues. Work through the codebase systematically rather than sampling files.
+
+## Procedure
+
+1. Identify the project structure, entry points, and external attack surface (network input, file input, shell commands).
+2. Scan for common issue classes:
+   - **Security**: injection (command/shell, path traversal), secrets in code, unsafe deserialization, missing auth/authorization, TLS misuse, dependency vulnerabilities (lockfile advisories).
+   - **Correctness**: race conditions, error paths swallowing failures, off-by-one / boundary errors, resource leaks (handles, sockets), unhandled promise rejections.
+   - **Quality**: dead code, duplicated logic, missing validation at boundaries, poor error messages, missing tests for critical paths.
+3. Verify suspicions against the actual code — cite file paths and line-level evidence.
+4. Report findings organized by severity (critical / high / medium / low), each with: location, what's wrong, why it matters, and a concrete fix suggestion.
+5. End with a short "healthy areas" note so the audit is balanced.
+
+## Constraints
+
+- Do not modify code during the audit — findings only.
+- If the project is small or has no security surface, say so explicitly instead of padding the report.

package/skills/bug/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: bug
+description: Use when the user reports a bug or asks to capture one — ask the minimal questions needed, then produce a structured bug report the team can act on.
+---
+
+# Bug Report
+
+Capture a complete, actionable bug report. Ask only the questions needed to fill genuine gaps — never interrogate the user.
+
+## Procedure
+
+1. Understand the symptom: what happened vs what was expected. If the user already gave enough detail, skip straight to the report.
+2. Fill any critical gaps with at most 2-3 targeted questions: reproduction steps, environment (OS/terminal/node version), and whether it's deterministic.
+3. If the codebase is available, inspect the suspected area to add root-cause hypotheses (with file/line evidence where possible).
+4. Produce the report:
+   - **标题**: one-line symptom summary
+   - **现象**: observed vs expected behavior
+   - **复现步骤**: minimal steps, with inputs
+   - **环境**: OS / node version / dsh-tui version / terminal
+   - **影响**: severity + who/what is affected
+   - **根因假设**: evidence-based guesses, clearly labeled as hypotheses
+   - **建议**: fix direction or workaround
+
+## Constraints
+
+- Never invent reproduction steps or environment details — mark unknowns as "待确认".
+- Keep the report tight; a bug report is a working document, not an essay.

package/skills/pr-comments/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: pr-comments
+description: Use when the user asks to review pull request comments, or when the /pr_comments command runs — fetch and analyze PR review comments on the current branch and summarize actionable items.
+---
+
+# Pull Request Comments Review
+
+Review the pull request comments associated with the current branch and turn them into an actionable summary.
+
+## Procedure
+
+1. Identify the PR for the current branch (git remote, branch name → PR). If no PR is found or git hosting tools are unavailable, say so and fall back to reviewing local uncommitted changes.
+2. Gather review comments (inline + general) and group them by theme: blocking changes, open questions, nits.
+3. For each actionable comment: restate the concern in your own words, locate the affected code, and propose a concrete change.
+4. Produce a summary: what the reviewers want changed, what's already addressed, and a suggested order of work.
+
+## Constraints
+
+- Never invent comments — summarize only what is actually there.
+- Mark unresolved vs resolved comments explicitly.

package/skills/practice/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: practice
+description: Use when the user asks to practice programming with dsh-tui, or wants to level up a specific skill through guided exercises.
+---
+
+# Programming Practice
+
+Run an interactive programming practice session with the user, adapting difficulty to their level and goals.
+
+## Procedure
+
+1. Ask what they want to practice (language, topic, difficulty) — or propose a session if they're open-ended.
+2. Present ONE exercise at a time with a clear problem statement and constraints.
+3. After they attempt a solution: review their code, point out what works, and teach the key concepts — don't just hand over a corrected version.
+4. Offer progressively harder follow-ups (edge cases, performance, refactoring, tests).
+5. Track their wins so later exercises build on them.
+
+## Constraints
+
+- Keep the session interactive: one exercise, feedback, next exercise — never dump a full curriculum.
+- Prefer Socratic hints over direct answers when the user is close.
+- Sessions should be completable in ~10-15 minutes per exercise.

package/skills/release-notes/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: release-notes
+description: Use when asked to generate release notes, or when the /release-notes command runs — derive user-facing release notes from the change history since the last release.
+---
+
+# Release Notes
+
+Generate user-facing release notes for the current project since the last release.
+
+## Procedure
+
+1. Determine the last release point (git tags) and collect the change set since then (git log / diff of user-facing surfaces).
+2. Classify changes:
+   - **新功能** (new features)
+   - **改进** (improvements / behavior changes)
+   - **修复** (bug fixes)
+   - **破坏性变更** (breaking changes — call these out first)
+   - **内部** (chore/refactor — omit from user-facing notes or fold into a footnote)
+3. Write notes in the user's language, focused on what changed for users — not implementation details.
+4. Reference issues/PRs where known, keep each bullet one line, group under the sections above.
+
+## Constraints
+
+- Do not fabricate changes — only what the history shows.
+- Breaking changes must be listed first, with migration hints.

package/skills/review/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: review
+description: Use when asked to review a codebase or a change, or when the /review command runs — assess design, correctness, maintainability, and test coverage with actionable feedback.
+---
+
+# Code Review
+
+Review the current project or the most recent change set and give feedback the author can act on.
+
+## Procedure
+
+1. Determine the review target: the whole project, the current branch diff (git diff against the base), or a specific area the user names.
+2. Read the code with these lenses:
+   - **设计**: does the structure match the problem? Clear ownership, sane seams, no over-engineering?
+   - **正确性**: boundary conditions, error handling, concurrency, resource lifetime.
+   - **可维护性**: naming, duplication, dead code, complexity hotspots, comment quality.
+   - **测试**: are the important behaviors covered? Are tests asserting behavior rather than implementation?
+3. For each finding: file/line, what's wrong, why it matters, concrete suggestion.
+4. Order feedback: blocking issues first, then nits. Distinguish "must fix" from "consider".
+5. End with what's good — reviews that only criticize are less useful.
+
+## Constraints
+
+- Do not modify code during the review.
+- If reviewing a diff, look at the diff in context (surrounding code), not just the changed lines.

package/skills/vuln-check/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: vuln-check
+description: Use when asked to check for security vulnerabilities, or when the /vuln-check command runs — scan the project for known vulnerable dependencies and security anti-patterns.
+---
+
+# Vulnerability Check
+
+Check the current project for security vulnerabilities: dependency advisories and code-level security anti-patterns.
+
+## Procedure
+
+1. **依赖审计**: inspect the lockfile/manifest (package-lock.json / pnpm-lock.yaml / requirements.txt…) for known-vulnerable versions. Use the local toolchain (npm audit / pnpm audit when available and network permits) or compare against known advisory data.
+2. **代码检查**: scan for security anti-patterns with file/line evidence:
+   - shell command injection (string interpolation into exec/spawn with shell:true)
+   - path traversal (user input joined into paths without normalization)
+   - secrets committed (API keys, tokens, private keys in the tree)
+   - unsafe eval / dynamic import of user input
+   - missing input validation at trust boundaries
+3. Report findings ordered by severity, each with: location, CVE/advisory id when applicable, impact, and remediation (upgrade to which version, or the code change needed).
+4. State explicitly when the project is clean in a category.
+
+## Constraints
+
+- Distinguish "verified vulnerable" from "needs verification" — never overstate.
+- Do not modify code during the check.