dsh-plugin-compose

Install and activate DSH plugins in isolated profiles using bundle patches and config dumps.

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/a179-sanae/dsh-code-check --skill dsh-plugin-compose-a179-sanae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dsh-plugin-compose
Source: https://github.com/a179-sanae/dsh-code-check/tree/main/.agents/skills/dsh-plugin-compose
Command: npx skills add https://github.com/a179-sanae/dsh-code-check --skill dsh-plugin-compose-a179-sanae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Wiring a standalone DSH plugin into a profile involves fragile steps: declaring the bundle patch in package.json, writing correct cordis.patch.yml rows, installing through dsh plugin, and proving the plugin actually activated. This Skill guides that composition workflow so overrides are not silently skipped and activation is verified rather than assumed. ## Core Features & Use Cases - Bundle Declaration Verification: Checks that package.json declares dsh.bundle.patch and that cordis.patch.yml ships in the manifest files list. - Patch Semantics Review: Enforces rules for id-targeted config replacement, insert rows, empty patch handling, and credential hygiene before installation. - Isolated Profile Installation: Installs packed artifacts, registry versions, or approved Git specs into a dedicated DSH_HOME without touching live profiles. - Activation Proof: Uses config dumps and real runner boot to confirm the plugin reaches its entry path, not just package resolution. - Use Case: After packing a new DSH plugin with pnpm pack, use this Skill to install it into a temporary profile, dump the effective config, and confirm the plugin's rows and behavior appear before shipping. ## Quick Start Use the dsh-plugin-compose skill to install this plugin into an isolated DSH profile, inspect the effective configuration, and prove it activates.

Frequently Asked Questions about dsh-plugin-compose

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install a DSH plugin into a profile?▼

Pack the plugin with pnpm pack, then pass the archive, registry spec, or approved Git spec to dsh plugin against an isolated profile. Confirm pnpm is on PATH first, since dsh plugin forwards package operations to it.

How do I verify a DSH plugin bundle is declared correctly?▼

Check that package.json contains a dsh.bundle.patch entry pointing at a shipped cordis.patch.yml, and that the patch file appears in the manifest files list. A dependency without dsh.bundle.patch installs but stays inactive as a bundle.

Why is my cordis.patch.yml override not taking effect?▼

Id-targeted patches replace the row's entire config value, so any field you omit is lost. Also, a patch targeting an absent id only warns on stderr; inspect the effective config dump to confirm the override landed.

Can I use link: or file: specs to install a DSH plugin?▼

No. Repository-relative link: or file: specs are disallowed because the package must first prove its own artifact is complete. Use pnpm pack and install the generated archive instead.

What happens when pnpm blocks a Git dependency build script?▼

pnpm 10 and later block lifecycle builds until allowed, so a source package with prepare may fail and print an allowBuilds key. Add only that printed key to the profile's pnpm-workspace.yaml and rerun the unchanged install.

How do I prove a DSH plugin actually activated?▼

Boot through the real runner or application entry and observe an effect specific to the plugin, not just package resolution or generic logs. Config dumps show composition, but activation requires reaching the plugin's real entry path.