[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FDEM07PDNZ9DBZF90CVDBZ":3,"skill-same:01M7FDEM07PDNZ9DBZF90CVDBZ":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7FDEM07PDNZ9DBZF90CVDBZ","dprint",null,"Runs dprint for the project. The first argument selects the action - init checks for the plugin's minimum dprint version, installs or updates dprint at user level after confirmation via AskUserQuestion, offers to create a dprint config when none exists and to add dprint plugins for file types the config does not cover; check [scope] runs dprint check; fmt [scope] runs dprint fmt and rewrites files; without an argument it runs fmt on the whole current directory. Use init when the user wants dprint set up, installed, updated, checked or its plugins completed; check when they want formatting verified with dprint; fmt only when they ask to format files with dprint. When invoking this skill yourself, always pass init, check or fmt as the first argument.","kwitsch\u002Fclaude-plugins-development","kwitsch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10324063?v=4","01M7FDD9EEY7P0P5C9QDQA74VK","Kwitsch","01M7FDD9FHJK7MPGWB04GTNV1M",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: dprint\ndescription: Runs dprint for the project. The first argument selects the action - init checks for the plugin's minimum dprint version, installs or updates dprint at user level after confirmation via AskUserQuestion, offers to create a dprint config when none exists and to add dprint plugins for file types the config does not cover; check [scope] runs dprint check; fmt [scope] runs dprint fmt and rewrites files; without an argument it runs fmt on the whole current directory. Use init when the user wants dprint set up, installed, updated, checked or its plugins completed; check when they want formatting verified with dprint; fmt only when they ask to format files with dprint. When invoking this skill yourself, always pass init, check or fmt as the first argument.\nargument-hint: \"[init|check|fmt] [scope]\"\nallowed-tools: [\"AskUserQuestion\", \"Bash(node:*)\"]\n---\n\n# dprint\n\nRuns one of three actions, selected by the first argument:\n\n- `init`: makes sure a usable dprint is installed, a dprint config exists and the config's plugins\n  cover the project's file types.\n- `check [scope]`: runs `dprint check` (read-only).\n- `fmt [scope]`: runs `dprint fmt`, which rewrites files in place.\n\nWithout any argument the skill runs `fmt` on the whole current working directory. `scope` limits\n`check` \u002F `fmt` to one file, directory or glob; without it dprint runs on the current directory.\ndprint may treat an explicit scope as overriding the config's `includes` (the `excludes` still\napply), so `fmt` with a scope can rewrite files the config leaves out.\n`check` and `fmt` need dprint and a project dprint config (in the current directory or an\nancestor up to the git root); when either is missing they run nothing and tell the user to run `\u002Fdprint init`\n(`\u002Fdprint:dprint init`) first.\n\n`init` makes sure a usable dprint (a native binary, or the dprint npm package via npx when no binary is\ninstalled), at least the minimum version pinned in `check-dprint.mjs`, is available. Detection is read-only. Installing or updating happens only after an explicit\n`Install` \u002F `Update` answer, and the command then runs visibly through the Bash tool (its normal\npermission prompt is a second gate; install\u002Fupdate commands are deliberately not pre-allowed).\nWith a usable dprint it then scans the project's file types against `dprint-plugins.json` and, per\nuncovered type, offers matching plugins; a plugin is added only after an explicit answer, via\n`dprint config add` through the normal Bash permission prompt. When the current directory has no\ndprint config, `init` offers to create one via `dprint init -y`, only after an explicit `Create`\nanswer.\n\n## Dispatch\n\nArguments: \"$ARGUMENTS\"\n\n1. Split the arguments above (empty when none were given):\n   - action: the first whitespace-separated word (case-sensitive).\n   - scope: everything after that word, trimmed. If the whole scope is enclosed in one matching\n     pair of `'` or `\"`, remove that pair. Alter nothing else: spaces inside stay, and the scope is\n     passed to dprint as one argument.\n2. Branch:\n   - No arguments at all: action `fmt` without scope; go to `## check \u002F fmt`.\n   - `check` or `fmt`: go to `## check \u002F fmt` with that scope (empty scope = no scope).\n   - `init` with an empty scope: go to `## init`, steps 1-8.\n   - `init` with a non-empty scope, or any other first word: print this line and stop, running\n     nothing:\n\n     ```text\n     usage: \u002Fdprint [init|check|fmt] [scope]  (no argument = fmt on the whole current directory)\n     ```\n\n## check \u002F fmt\n\n1. Read `${CLAUDE_SKILL_DIR}\u002Frun-dprint.reference.md` (output and exit-code contract).\n2. From the current working directory, run exactly one Bash command. Without a scope:\n\n   ```text\n   node ${CLAUDE_SKILL_DIR}\u002Frun-dprint.mjs \u003Ccheck|fmt>\n   ```\n\n   With a scope, single-quote it so the shell passes it unchanged and expands no globs; write each\n   `'` inside the scope as `'\\''`:\n\n   ```text\n   node ${CLAUDE_SKILL_DIR}\u002Frun-dprint.mjs \u003Ccheck|fmt> '\u003Cscope>'\n   ```\n\n3. Branch on the exit code. No retry in any case:\n   - `3` (not set up): tell the user that dprint must first be initialized with `\u002Fdprint init`\n     (`\u002Fdprint:dprint init`) and name the reason from the `status=notsetup reason=` line\n     (`missing` = no dprint found, `noconfig` = no dprint config in this directory or its\n     ancestors up to the git root). Run nothing else and never start init on your own.\n   - `0`: report success; for `fmt`, quote dprint's summary line if it printed one.\n   - `20` (`check`): list the unformatted files from the output and mention `\u002Fdprint fmt` with the\n     same scope.\n   - `14`: report that no files matched the scope.\n   - `2`: report the stderr diagnostic.\n   - Any other code: report dprint's error output and the exit code.\n\n## init\n\n1. **All questions go through the `AskUserQuestion` tool, never as plain text.** Never run an\n   install or update command without an explicit `Install` \u002F `Update` answer. Never run\n   `config add` without an explicit answer naming that plugin. Never run `\u003Cdprint> init -y` without\n   an explicit `Create` answer.\n\n2. Read `${CLAUDE_SKILL_DIR}\u002Fcheck-dprint.reference.md` (output line and exit-code contract).\n\n3. Run the check:\n\n   ```bash\n   node ${CLAUDE_SKILL_DIR}\u002Fcheck-dprint.mjs\n   ```\n\n   Parse `status`, `version`, `min` and `path` from its single stdout line. From here on,\n   **`\u003Cdprint>`** means `\u003Cpath>`, or `npx --yes dprint` when `path` is `npx` (dprint runs through\n   npx because no binary is installed). Branch on the exit code, per the table in\n   `check-dprint.reference.md`:\n   - `0` (ok): report `dprint \u003Cversion> at \u003Cpath> (>= \u003Cmin>)`, or `dprint \u003Cversion> via npx (>= \u003Cmin>)`\n     when `path` is `npx`, and go to step 7. Ask nothing about installing.\n   - `2` (error): report the stderr diagnostic and stop. Never guess, never install.\n   - `10` (missing) or `11` (outdated): go to step 4.\n\n4. Ask exactly one `AskUserQuestion`, single-select (`multiSelect: false`), no pre-selected option:\n   - **missing** (exit 10):\n     - header: `dprint [currently: not installed]`\n     - question: `Install dprint (minimum \u003Cmin>) to ~\u002F.dprint\u002Fbin (or $DPRINT_INSTALL\u002Fbin when set) via the official installer?`\n     - options: `Install`, described as \"Runs curl -fsSL https:\u002F\u002Fdprint.dev\u002Finstall.sh | sh\";\n       `Skip`, described as \"Install nothing.\"\n   - **outdated** (exit 11) with `path` = `npx` (`upgrade` does not apply to npx):\n     - header: `dprint [currently: \u003Cversion> via npx, needs >= \u003Cmin>]`\n     - question: `Install dprint (minimum \u003Cmin>) to ~\u002F.dprint\u002Fbin (or $DPRINT_INSTALL\u002Fbin when set) via the official installer? It takes precedence over npx.`\n     - options: `Install`, described as \"Runs curl -fsSL https:\u002F\u002Fdprint.dev\u002Finstall.sh | sh\";\n       `Skip`, described as \"Install nothing.\"\n   - **outdated** (exit 11) with an absolute `path`:\n     - header: `dprint [currently: \u003Cversion>, needs >= \u003Cmin>]`\n     - question: `Update dprint at \u003Cpath>?`\n     - options: `Update`, described as the exact update command chosen in step 5 (for example\n       \"Runs \u003Cpath> upgrade\"); `Skip`, described as \"Change nothing.\"\n   - `Skip`, or any answer other than `Install` \u002F `Update`: report \"skipped, nothing changed\" and\n     stop (no plugin scan without a usable dprint).\n\n5. Apply only after `Install` \u002F `Update`, via the Bash tool, one command, visibly:\n   - **Install:**\n\n     ```bash\n     curl -fsSL https:\u002F\u002Fdprint.dev\u002Finstall.sh | sh\n     ```\n\n   - **Update** (every outdated version has the `upgrade` subcommand, since the minimum is far\n     above 0.30.0):\n\n     ```text\n     \u003Cpath> upgrade\n     ```\n\n   - Non-zero exit (or the permission prompt is denied): report the command's error output and\n     stop. No retry, no fallback to another install method.\n\n6. Re-run the check:\n\n   ```bash\n   node ${CLAUDE_SKILL_DIR}\u002Fcheck-dprint.mjs\n   ```\n\n   - Exit `0`: report the new version and path. If `path` is `\u003Chome>\u002F.dprint\u002Fbin\u002Fdprint` (or `$DPRINT_INSTALL\u002Fbin\u002Fdprint`; use that directory in the line below), also\n     check whether that directory is on `PATH` with `node -e \"console.log(process.env.PATH)\"`. If\n     it is not, print this line for the user to add to their shell profile (never edit shell rc\n     files yourself):\n\n     ```bash\n     export PATH=\"$HOME\u002F.dprint\u002Fbin:$PATH\"\n     ```\n\n     Then go to step 7.\n\n   - Non-zero exit: report the state and stop. If it is still `outdated` after the upgrade,\n     dprint is likely managed by a package manager (npm, Homebrew, ...) that refused the\n     self-upgrade: tell the user to update it through that package manager. Never force a\n     reinstall that would shadow the managed copy.\n\n7. **Plugin coverage.** Only reached with exit `0` from step 3 or step 6. `\u003Cdprint>` is built (as\n   defined in step 3) from the `path` of that check.\n   1. Read `${CLAUDE_SKILL_DIR}\u002Fscan-plugins.reference.md` (output lines and exit-code contract).\n   2. From the project root, run the scan and report every stderr line:\n\n      ```bash\n      node ${CLAUDE_SKILL_DIR}\u002Fscan-plugins.mjs\n      ```\n\n      Parse `status`, `config` and `missing` from the first stdout line and `type`, `files` and\n      `candidates` from each following line, then branch on the exit code:\n      - `0` (ok): report \"`\u003Cconfig>` covers every detected file type\" and go to step 8.\n      - `11` (noconfig): if the create question was not yet asked in this run, ask exactly one\n        `AskUserQuestion`, single-select (`multiSelect: false`), no pre-selected option:\n        - header: `dprint config`\n        - question:\n          `No dprint config (dprint.json, dprint.jsonc, .dprint.json, .dprint.jsonc, .config\u002Fdprint.json, .config\u002Fdprint.jsonc) in the current directory or an ancestor up to the git root. Create dprint.json here with plugins for the file types found?`\n        - options: `Create`, described as \"Runs `\u003Cdprint> init -y`\"; `Skip`, described as \"Create\n          no config; the plugin scan, check and fmt need one.\"\n        - `Create`: run it via the Bash tool, one command, visibly (its normal permission prompt\n          applies):\n\n          ```text\n          \u003Cdprint> init -y\n          ```\n\n          Non-zero exit (or the permission prompt is denied): report the command's error output\n          and go to step 8. Success: go to step 7.5.\n        - `Skip`, any other answer, or the question was already asked in this run: report \"no\n          dprint config; plugin scan skipped\" and go to step 8.\n      - `2` (error): report the stderr diagnostic and go to step 8.\n      - `10` (missing): continue with step 7.3.\n\n   3. Take the first `type=` line whose type has not been asked about in this run. If there is\n      none, go to step 8. Ask exactly one `AskUserQuestion`, single-select\n      (`multiSelect: false`), no pre-selected option:\n      - header: the type (for example `.ts`, `Dockerfile`), cut to 12 characters\n      - question with one candidate:\n        `No plugin in \u003Cconfig> formats \u003Ctype> files (\u003Cfiles> found). Add the dprint plugin \u003Ccandidate>?`\n      - question with several candidates:\n        `No plugin in \u003Cconfig> formats \u003Ctype> files (\u003Cfiles> found). Which dprint plugin should format them?`\n        With more than 3 candidates, append\n        `Other candidates (type the exact name via Other): \u003C4th>, \u003C5th>, ...`\n      - options: the first 3 candidates in output order, each labelled with the candidate name and\n        described as \"Runs `\u003Cdprint> config add \u003Ccandidate>`\"; then `Skip`, described as \"Add nothing\n        for `\u003Ctype>`.\"\n      - The chosen plugin is the selected candidate label, or an \"Other\" answer that exactly\n        equals one of this line's candidates: go to step 7.4.\n      - `Skip`, or any other answer: record `\u003Ctype>` as skipped and go to step 7.5.\n   4. Add the chosen plugin via the Bash tool, one command, visibly:\n\n      ```text\n      \u003Cdprint> config add \u003Ccandidate>\n      ```\n\n      Non-zero exit (or the permission prompt is denied): report the command's error output, ask\n      nothing further and go to step 8. No retry.\n\n   5. Re-run `node ${CLAUDE_SKILL_DIR}\u002Fscan-plugins.mjs` (an added plugin may cover further types)\n      and branch as in step 7.2, except that exit `10` goes back to step 7.3.\n\n8. Final output, as a terse bullet list:\n   - state before (`status`, `version`, `path`)\n   - action taken (command run, or \"skipped\")\n   - state after (`status`, `version`, `path`, plus the `export PATH` line when needed)\n   - plugin scan: config file (and the `\u003Cdprint> init -y` command run when step 7.2 created it),\n     plugins added (each `config add` command run), types skipped, types still uncovered. If the\n     scan did not run, say why.\n","# dprint\n\nRuns one of three actions, selected by the first argument:\n\n- `init`: makes sure a usable dprint is installed, a dprint config exists and the config's plugins\n  cover the project's file types.\n- `check [scope]`: runs `dprint check` (read-only).\n- `fmt [scope]`: runs `dprint fmt`, which rewrites files in place.\n\nWithout any argument the skill runs `fmt` on the whole current working directory. `scope` limits\n`check` \u002F `fmt` to one file, directory or glob; without it dprint runs on the current directory.\ndprint may treat an explicit scope as overriding the config's `includes` (the `excludes` still\napply), so `fmt` with a scope can rewrite files the config leaves out.\n`check` and `fmt` need dprint and a project dprint config (in the current directory or an\nancestor up to the git root); when either is missing they run nothing and tell the user to run `\u002Fdprint init`\n(`\u002Fdprint:dprint init`) first.\n\n`init` makes sure a usable dprint (a native binary, or the dprint npm package via npx when no binary is\ninstalled), at least the minimum version pinned in `check-dprint.mjs`, is available. Detection is read-only. Installing or updating happens only after an explicit\n`Install` \u002F `Update` answer, and the command then runs visibly through the Bash tool (its normal\npermission prompt is a second gate; install\u002Fupdate commands are deliberately not pre-allowed).\nWith a usable dprint it then scans the project's file types against `dprint-plugins.json` and, per\nuncovered type, offers matching plugins; a plugin is added only after an explicit answer, via\n`dprint config add` through the normal Bash permission prompt. When the current directory has no\ndprint config, `init` offers to create one via `dprint init -y`, only after an explicit `Create`\nanswer.\n\n## Dispatch\n\nArguments: \"$ARGUMENTS\"\n\n1. Split the arguments above (empty when none were given):\n   - action: the first whitespace-separated word (case-sensitive).\n   - scope: everything after that word, trimmed. If the whole scope is enclosed in one matching\n     pair of `'` or `\"`, remove that pair. Alter nothing else: spaces inside stay, and the scope is\n     passed to dprint as one argument.\n2. Branch:\n   - No arguments at all: action `fmt` without scope; go to `## check \u002F fmt`.\n   - `check` or `fmt`: go to `## check \u002F fmt` with that scope (empty scope = no scope).\n   - `init` with an empty scope: go to `## init`, steps 1-8.\n   - `init` with a non-empty scope, or any other first word: print this line and stop, running\n     nothing:\n\n     ```text\n     usage: \u002Fdprint [init|check|fmt] [scope]  (no argument = fmt on the whole current directory)\n     ```\n\n## check \u002F fmt\n\n1. Read `${CLAUDE_SKILL_DIR}\u002Frun-dprint.reference.md` (output and exit-code contract).\n2. From the current working directory, run exactly one Bash command. Without a scope:\n\n   ```text\n   node ${CLAUDE_SKILL_DIR}\u002Frun-dprint.mjs \u003Ccheck|fmt>\n   ```\n\n   With a scope, single-quote it so the shell passes it unchanged and expands no globs; write each\n   `'` inside the scope as `'\\''`:\n\n   ```text\n   node ${CLAUDE_SKILL_DIR}\u002Frun-dprint.mjs \u003Ccheck|fmt> '\u003Cscope>'\n   ```\n\n3. Branch on the exit code. No retry in any case:\n   - `3` (not set up): tell the user that dprint must first be initialized with `\u002Fdprint init`\n     (`\u002Fdprint:dprint init`) and name the reason from the `status=notsetup reason=` line\n     (`missing` = no dprint found, `noconfig` = no dprint config in this directory or its\n     ancestors up to the git root). Run nothing else and never start init on your own.\n   - `0`: report success; for `fmt`, quote dprint's summary line if it printed one.\n   - `20` (`check`): list the unformatted files from the output and mention `\u002Fdprint fmt` with the\n     same scope.\n   - `14`: report that no files matched the scope.\n   - `2`: report the stderr diagnostic.\n   - Any other code: report dprint's error output and the exit code.\n\n## init\n\n1. **All questions go through the `AskUserQuestion` tool, never as plain text.** Never run an\n   install or update command without an explicit `Install` \u002F `Update` answer. Never run\n   `config add` without an explicit answer naming that plugin. Never run `\u003Cdprint> init -y` without\n   an explicit `Create` answer.\n\n2. Read `${CLAUDE_SKILL_DIR}\u002Fcheck-dprint.reference.md` (output line and exit-code contract).\n\n3. Run the check:\n\n   ```bash\n   node ${CLAUDE_SKILL_DIR}\u002Fcheck-dprint.mjs\n   ```\n\n   Parse `status`, `version`, `min` and `path` from its single stdout line. From here on,\n   **`\u003Cdprint>`** means `\u003Cpath>`, or `npx --yes dprint` when `path` is `npx` (dprint runs through\n   npx because no binary is installed). Branch on the exit code, per the table in\n   `check-dprint.reference.md`:\n   - `0` (ok): report `dprint \u003Cversion> at \u003Cpath> (>= \u003Cmin>)`, or `dprint \u003Cversion> via npx (>= \u003Cmin>)`\n     when `path` is `npx`, and go to step 7. Ask nothing about installing.\n   - `2` (error): report the stderr diagnostic and stop. Never guess, never install.\n   - `10` (missing) or `11` (outdated): go to step 4.\n\n4. Ask exactly one `AskUserQuestion`, single-select (`multiSelect: false`), no pre-selected option:\n   - **missing** (exit 10):\n     - header: `dprint [currently: not installed]`\n     - question: `Install dprint (minimum \u003Cmin>) to ~\u002F.dprint\u002Fbin (or $DPRINT_INSTALL\u002Fbin when set) via the official installer?`\n     - options: `Install`, described as \"Runs curl -fsSL https:\u002F\u002Fdprint.dev\u002Finstall.sh | sh\";\n       `Skip`, described as \"Install nothing.\"\n   - **outdated** (exit 11) with `path` = `npx` (`upgrade` does not apply to npx):\n     - header: `dprint [currently: \u003Cversion> via npx, needs >= \u003Cmin>]`\n     - question: `Install dprint (minimum \u003Cmin>) to ~\u002F.dprint\u002Fbin (or $DPRINT_INSTALL\u002Fbin when set) via the official installer? It takes precedence over npx.`\n     - options: `Install`, described as \"Runs curl -fsSL https:\u002F\u002Fdprint.dev\u002Finstall.sh | sh\";\n       `Skip`, described as \"Install nothing.\"\n   - **outdated** (exit 11) with an absolute `path`:\n     - header: `dprint [currently: \u003Cversion>, needs >= \u003Cmin>]`\n     - question: `Update dprint at \u003Cpath>?`\n     - options: `Update`, described as the exact update command chosen in step 5 (for example\n       \"Runs \u003Cpath> upgrade\"); `Skip`, described as \"Change nothing.\"\n   - `Skip`, or any answer other than `Install` \u002F `Update`: report \"skipped, nothing changed\" and\n     stop (no plugin scan without a usable dprint).\n\n5. Apply only after `Install` \u002F `Update`, via the Bash tool, one command, visibly:\n   - **Install:**\n\n     ```bash\n     curl -fsSL https:\u002F\u002Fdprint.dev\u002Finstall.sh | sh\n     ```\n\n   - **Update** (every outdated version has the `upgrade` subcommand, since the minimum is far\n     above 0.30.0):\n\n     ```text\n     \u003Cpath> upgrade\n     ```\n\n   - Non-zero exit (or the permission prompt is denied): report the command's error output and\n     stop. No retry, no fallback to another install method.\n\n6. Re-run the check:\n\n   ```bash\n   node ${CLAUDE_SKILL_DIR}\u002Fcheck-dprint.mjs\n   ```\n\n   - Exit `0`: report the new version and path. If `path` is `\u003Chome>\u002F.dprint\u002Fbin\u002Fdprint` (or `$DPRINT_INSTALL\u002Fbin\u002Fdprint`; use that directory in the line below), also\n     check whether that directory is on `PATH` with `node -e \"console.log(process.env.PATH)\"`. If\n     it is not, print this line for the user to add to their shell profile (never edit shell rc\n     files yourself):\n\n     ```bash\n     export PATH=\"$HOME\u002F.dprint\u002Fbin:$PATH\"\n     ```\n\n     Then go to step 7.\n\n   - Non-zero exit: report the state and stop. If it is still `outdated` after the upgrade,\n     dprint is likely managed by a package manager (npm, Homebrew, ...) that refused the\n     self-upgrade: tell the user to update it through that package manager. Never force a\n     reinstall that would shadow the managed copy.\n\n7. **Plugin coverage.** Only reached with exit `0` from step 3 or step 6. `\u003Cdprint>` is built (as\n   defined in step 3) from the `path` of that check.\n   1. Read `${CLAUDE_SKILL_DIR}\u002Fscan-plugins.reference.md` (output lines and exit-code contract).\n   2. From the project root, run the scan and report every stderr line:\n\n      ```bash\n      node ${CLAUDE_SKILL_DIR}\u002Fscan-plugins.mjs\n      ```\n\n      Parse `status`, `config` and `missing` from the first stdout line and `type`, `files` and\n      `candidates` from each following line, then branch on the exit code:\n      - `0` (ok): report \"`\u003Cconfig>` covers every detected file type\" and go to step 8.\n      - `11` (noconfig): if the create question was not yet asked in this run, ask exactly one\n        `AskUserQuestion`, single-select (`multiSelect: false`), no pre-selected option:\n        - header: `dprint config`\n        - question:\n          `No dprint config (dprint.json, dprint.jsonc, .dprint.json, .dprint.jsonc, .config\u002Fdprint.json, .config\u002Fdprint.jsonc) in the current directory or an ancestor up to the git root. Create dprint.json here with plugins for the file types found?`\n        - options: `Create`, described as \"Runs `\u003Cdprint> init -y`\"; `Skip`, described as \"Create\n          no config; the plugin scan, check and fmt need one.\"\n        - `Create`: run it via the Bash tool, one command, visibly (its normal permission prompt\n          applies):\n\n          ```text\n          \u003Cdprint> init -y\n          ```\n\n          Non-zero exit (or the permission prompt is denied): report the command's error output\n          and go to step 8. Success: go to step 7.5.\n        - `Skip`, any other answer, or the question was already asked in this run: report \"no\n          dprint config; plugin scan skipped\" and go to step 8.\n      - `2` (error): report the stderr diagnostic and go to step 8.\n      - `10` (missing): continue with step 7.3.\n\n   3. Take the first `type=` line whose type has not been asked about in this run. If there is\n      none, go to step 8. Ask exactly one `AskUserQuestion`, single-select\n      (`multiSelect: false`), no pre-selected option:\n      - header: the type (for example `.ts`, `Dockerfile`), cut to 12 characters\n      - question with one candidate:\n        `No plugin in \u003Cconfig> formats \u003Ctype> files (\u003Cfiles> found). Add the dprint plugin \u003Ccandidate>?`\n      - question with several candidates:\n        `No plugin in \u003Cconfig> formats \u003Ctype> files (\u003Cfiles> found). Which dprint plugin should format them?`\n        With more than 3 candidates, append\n        `Other candidates (type the exact name via Other): \u003C4th>, \u003C5th>, ...`\n      - options: the first 3 candidates in output order, each labelled with the candidate name and\n        described as \"Runs `\u003Cdprint> config add \u003Ccandidate>`\"; then `Skip`, described as \"Add nothing\n        for `\u003Ctype>`.\"\n      - The chosen plugin is the selected candidate label, or an \"Other\" answer that exactly\n        equals one of this line's candidates: go to step 7.4.\n      - `Skip`, or any other answer: record `\u003Ctype>` as skipped and go to step 7.5.\n   4. Add the chosen plugin via the Bash tool, one command, visibly:\n\n      ```text\n      \u003Cdprint> config add \u003Ccandidate>\n      ```\n\n      Non-zero exit (or the permission prompt is denied): report the command's error output, ask\n      nothing further and go to step 8. No retry.\n\n   5. Re-run `node ${CLAUDE_SKILL_DIR}\u002Fscan-plugins.mjs` (an added plugin may cover further types)\n      and branch as in step 7.2, except that exit `10` goes back to step 7.3.\n\n8. Final output, as a terse bullet list:\n   - state before (`status`, `version`, `path`)\n   - action taken (command run, or \"skipped\")\n   - state after (`status`, `version`, `path`, plus the `export PATH` line when needed)\n   - plugin scan: config file (and the `\u003Cdprint> init -y` command run when step 7.2 created it),\n     plugins added (each `config add` command run), types skipped, types still uncovered. If the\n     scan did not run, say why.\n",{"name":5,"description":7,"allowed-tools":24,"argument-hint":27},[25,26],"AskUserQuestion","Bash(node:*)","[init|check|fmt] [scope]","main","bb893ea76ba6e0d3f64bb1f59d9020751fc5d618","dprint\u002Fplugin\u002Fskills\u002Fdprint","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development","https:\u002F\u002Fgithub.com\u002Fkwitsch","2026-11-15 18:25:39",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add kwitsch\u002Fclaude-plugins-development --skill dprint",{"tool":40,"command":41},"bunx","bunx skills add kwitsch\u002Fclaude-plugins-development --skill dprint",{"tool":43,"command":44},"pnpm","pnpm dlx skills add kwitsch\u002Fclaude-plugins-development --skill dprint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002FSKILL.md",true,[48,54,60,64,68,72,76,80,84,88],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"check-dprint.mjs","SCRIPT","脚本",1364,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Fcheck-dprint.mjs",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"check-dprint.reference.md","REFERENCE","参考文档",3372,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Fcheck-dprint.reference.md",{"path":61,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":62,"sourceHtmlUrl":63},"config-names.mjs",134,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Fconfig-names.mjs",{"path":65,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":66,"sourceHtmlUrl":67},"dprint-plugins.json",5628,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Fdprint-plugins.json",{"path":69,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":70,"sourceHtmlUrl":71},"find-config.mjs",538,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Ffind-config.mjs",{"path":73,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":74,"sourceHtmlUrl":75},"find-dprint.mjs",1377,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Ffind-dprint.mjs",{"path":77,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":78,"sourceHtmlUrl":79},"run-dprint.mjs",985,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Frun-dprint.mjs",{"path":81,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":82,"sourceHtmlUrl":83},"run-dprint.reference.md",5132,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Frun-dprint.reference.md",{"path":85,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":86,"sourceHtmlUrl":87},"scan-plugins.mjs",3077,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Fscan-plugins.mjs",{"path":89,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":90,"sourceHtmlUrl":91},"scan-plugins.reference.md",5231,"https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fdprint\u002Fplugin\u002Fskills\u002Fdprint\u002Fscan-plugins.reference.md",[93,100,107,114,121,128],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FDF4DKMYQ2TTKD6TBJ6T0B","universal-lint","User-invoked. Takes a free-text description of a set of files (\"all files in src\u002F\", \"files changed in PR 123\", or an explicit list) and lints each of them exactly as this plugin's Write\u002FEdit hook would — read-only, no autofix — printing one aggregated findings report. Self-contained: depends on no other plugin.","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Funiversal-lint\u002Fplugin\u002Fskills\u002Funiversal-lint\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FDEXH3PZGS7PPQBNV9RTRS","solve","Single entry point for any coding task (change, feature, refactor, bug). Triages the task through the jev-api tools and routes it to the right track, loading the phase references it needs. Flags --headless (the decider agent answers every question) and --size=\u003CS|M|L|XL>. Use when the user hands over a task to implement or fix.","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002Fjev-solver\u002Fplugin\u002Fskills\u002Fsolve\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7FDEENDBD9H0PK0BM3CG0CX","split-hooks-lib","Split the hooks module of a function-hooks plugin of this repository into a readable entry register.mts plus helper modules that the build bundles into one compressed plugin\u002Fhooks\u002Flib.mjs, to keep the shipped size small. Use when the user asks to split a plugin's register.mts, to make a plugin smaller, to move a plugin to register.mjs plus lib.mjs, or when a hooks module has grown too large for one file.","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fsplit-hooks-lib\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7FDEBDF3CXHKQ9XDXRTT7RC","__SKILL_NAME__","__SKILL_DESCRIPTION__ Use when the user asks to …","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fscaffold-plugin\u002Ftemplates\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7FDE5RSE231MVBRWM69TJ30","scaffold-plugin","Scaffold a new Claude Code plugin in this repository with the repo layout (\u003Cname>\u002Fpackage.json, plugin\u002F, src\u002F, tests\u002F). Use when the user asks to create, add, scaffold or start a new plugin here.","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fscaffold-plugin\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M7FDDZJ5W6XY9SJ2HMS6H5YT","refactor-plugin","Refactor one plugin of this repository end to end in a fresh worktree on its own branch cut from a freshly fetched origin\u002Fmain - perf-worklist, then bughunt, then a merge-ready PR. Use when the user asks to refactor, overhaul or run the full performance and bug hunt pass on a plugin.","https:\u002F\u002Fgithub.com\u002Fkwitsch\u002Fclaude-plugins-development\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frefactor-plugin\u002FSKILL.md",[],[]]