DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to upgrade an old DSH plugin to a new DSH release with Awesome DeepSeek Harness

Use an upgrade skill pack so Claude Code or Codex can migrate a plugin to a newer DSH version.

Who it is forA plugin author whose DSH plugin broke after a new DSH release and who wants an agent to do the migration.

The problemMigrating a plugin across DSH versions means tracking breaking changes by hand.

The outcomeAn agent lists the breaking changes, patches the plugin, tests it and prepares it for publishing.

What you need first

  • DeepSeek Harness (DSH) installed, with the dsh command available
  • Access to the target plugin repo on GitHub, which should carry the #dsh topic
  • A DSH profile to install plugins into (the examples use the profile name web)

Steps

  1. Run npx @deepseek-ai/dsh web to confirm DSH runs before you start the migration.
  2. Clone or open the upgrade skill repo at github.com/oh-my-dsh/dsh-plugin-upgrade-skill in the agent's workspace. (inferred, check the README)
  3. Give the agent the path to your old plugin and the target DSH version.
  4. Have the agent list the breaking changes, patch the plugin and run its tests.
  5. Review the patch and test results before publishing the plugin.

Prompt for your agent

Using the upgrade skills in github.com/oh-my-dsh/dsh-plugin-upgrade-skill, migrate the DSH plugin at <plugin-path> to the target DSH version <target-version>. Report the list of breaking changes applied and the test result. Verify by running the plugin's tests and confirming they pass.

Caveat. The skill pack targets specific DSH release versions, so confirm your target version is covered before running it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page