Dsh Rename

Not checkedunknownfresh

DeepSeek Harness slash command: /rename with a name, or let the model summarize the conversation and pick one

Install Dsh Rename

Every command below is generated from this repository’s own package.json.

Not checked — and that is not the same as fine

We could not find a package.json for this repository, so none of the publish spec rules could be applied. We do not know whether dsh plugin add activates anything here.

Best-effort git install — unverified, may activate nothing

# 1. add the bundle to a profile — --profile my-profile points at $DSH_HOME/profiles/my-profile
dsh plugin --profile my-profile add github:lmst2/dsh-rename

# 2. verify: the bundle should show up as a layer in the resolved config
dsh --profile my-profile --dump-config

# 3. boot the profile
dsh --profile my-profile

Step 2 is the one that matters here: if --dump-config shows no new layer after the install, this repository is not a bundle and there is nothing to activate.

Before you run it

A plugin runs with your permissions once loaded: it can read your files, use your credentials and reach the network. Tool approvals do not sandbox it.
Installing from git resolves a moving branch. Pin a commit — github:lmst2/dsh-rename#<commit-sha> — so the code you reviewed is the code you install.

Prerequisites

API key: Not determined from the README.
Network access: Not determined from the README.
Language: TypeScript

Install check

Every field the verdict was derived from, so you can re-derive it yourself

No check record is stored for this entry yet. That is why its verdict is Not checked — nothing was verified, which is not the same as nothing being wrong.