dsh_plugin_swift_cycle: A Project Governance Skill Adapter for DeepSeek Harness

Swift Cycle is a project governance skill adapter (DSH plugin) for DeepSeek Harness, maintained by Solismuchengxue under the MIT license. It registers the pinned Swift Cycle v1.2.0 payload as a Harness Skill that can only be explicitly invoked by users, addressing the uncontrollability of model-implicit calls in governance workflows. Core capabilities include Knowledge Promotion, State Separation, Governance Baseline, Commit Boundary Planning, and Source/Runtime Boundary, covering the full governance chain from knowledge promotion to commit boundary planning. Adapter version 0.1.1 has passed local source verification, candidate artifact preflight, and read-only smoke tests in an isolated Harness Runtime, ensuring verifiable distribution and operation.

What core governance capabilities does the Swift Cycle DSH plugin support?

Swift Cycle encapsulates the upstream Swift Cycle v1.2.0 governance rules into five capabilities: Knowledge Promotion promotes long-lived shared facts into Git-managed assets; State Separation separates engineering, experiment, quality, and release conclusions; Governance Baseline records a comparable baseline before complex governance; Commit Boundary Planning pre-divides single-intent and validation boundaries for multi-commit work; Source/Runtime Boundary separately validates source, artifacts, runtime, and actual consumers. The complete governance rules are governed by the pinned upstream SKILL.md; this README does not copy the Skill body.

How do I install the Swift Cycle DSH plugin?

For daily installation, use npm latest; for a pinned, reproducible install, specify the version or install from a GitHub fixed commit. It is recommended to check the composite config before installing or modifying profiles. The following commands must be run in a DSH environment:

dsh plugin --profile web add github:solismuchengxue/dsh_plugin_swift_cycle

For a pinned version, specify the npm version or the full 40-character GitHub commit (e.g., corresponding to v0.1.1). After installation, you can check the config with dsh --profile web --dump-config.

How do I invoke the Swift Cycle DSH plugin?

The adapter registers with modelInvocable = false and userInvocable = true, so Swift Cycle does not enter the model-implicitly selectable Skill directory; users must explicitly type /swift-cycle to invoke it. This ensures governance processes are always user-triggered, preventing the model from automatically executing governance operations.

How do I locally verify the Swift Cycle DSH plugin?

Requires Node.js 20 or higher; the package has no runtime dependencies and does not execute installation lifecycle scripts. Run npm test for tests, npm run verify:upstream to verify upstream consistency, and npm run pack:dry-run to preflight candidate artifacts. Maintainers can also explicitly provide a Swift Cycle checkout for read-only payload comparison: node scripts/verify-upstream.mjs --source "<path>". The adapter does not access the network, read credentials, or modify user-level Skill directories during loading and runtime.

What is the verification boundary of the Swift Cycle DSH plugin?

According to the pinned DeepSeek Harness Skill Registry rules, project-level same-name entries can override the adapter's Runtime registration, but the adapter does not delete or rewrite shadowed Skills. Verification must cover four layers separately: Git source matches upstream lock, npm pack candidate artifact content is correct, isolated Harness Runtime can register and explicitly invoke, and real user profile is installed and used by actual consumers. Current evidence covers one read-only invocation each in an empty workspace and a non-empty Git project, and does not represent verification of other projects, write flows, or production governance.

View more DSH plugins at dsh-plugin.org