dsh-plugin-scaffold

Creates standalone DSH plugin repositories from a self-contained template with baseline verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a new DSH plugin repository by hand is error-prone: package identity, Cordis plugin ids, peer dependencies, TypeScript build topology, and lockfiles must all agree before any behavior code can be written. This Skill turns the plugin-template into a repeatable, verified scaffolding workflow. ## Core Features & Use Cases - Template Copying with Guardrails: Copies only source-controlled template files, preserves the dual build paths (tsc -b plus tsdown, and the prepare-based git install path), and refuses to overwrite an existing non-empty target directory. - Identity Replacement: Updates package.json, src/index.ts, config, runtime, invariant, tests, cordis.patch.yml, tsconfigs, and docs, then greps for leftover template placeholders. - Dependency and Type Alignment: Keeps peerDependencies, registry dev dependencies, tsconfig settings, Vitest aliases, and cordis.patch.yml inject entries consistent, forbidding link:/file: dependencies and external project references. - Baseline Verification: Runs pnpm install, verify:self-contained, typecheck, test, build, and prepare before any product behavior is added. - Use Case: After planning a new DSH plugin, hand the Skill a target directory, package name, and plugin id, and receive a clean repository whose skeleton builds, tests, and bundles out of the box. ## Quick Start Use $dsh-plugin-scaffold to create a new standalone plugin repository from plugin-template into the target directory with my chosen package name and plugin id.

Frequently Asked Questions about dsh-plugin-scaffold

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

FAQPage Schema
How do I create a new DSH plugin repository from the template?▼

Provide the target directory, package name, Cordis plugin id, description, and dependency matrix, then run the scaffold workflow. It copies source-controlled template files, replaces identity in package.json, src, tests, and cordis.patch.yml, generates the lockfile, and runs the baseline verification commands.

What inputs are required before scaffolding a DSH plugin?▼

The handoff requires target, packageName, pluginId, description, plugin form, dependency matrix, target profile, invariant decision, distribution assumption, and the template source directory. Names are validated before any copying begins.

Can I scaffold into an existing non-empty directory?▼

No. If the target exists and is non-empty, the Skill asks whether this is an audit or merge task and never replaces it as scaffolding. This prevents unguarded recursive deletes and accidental data loss.

Does the template allow link: or file: dependencies?▼

No. The template forbids local link: and file: dependencies and forbids project references that leave the repository. Every fresh clone must resolve its build graph from its own manifest and pnpm lockfile.

Why does the scaffold run pnpm build and prepare before adding features?▼

Baseline verification proves the unchanged skeleton works: install, verify:self-contained, typecheck, test, build, and prepare must pass first. This isolates template problems from later behavior code and keeps failures attributable.