Preface

When performing project governance in DeepSeek Harness (DSH), a common practice is to write ad-hoc prompts or scatter rules across conversations. The problem is: long-term shared facts are difficult to persist into Git assets, engineering, experiments, quality, and release conclusions can easily become entangled, and there is no comparable baseline before complex governance begins.

dsh_plugin_swift_cycle is a DSH adapter for Swift Cycle. It registers the locked Swift Cycle v1.2.0 payload as a Harness Skill that can only be explicitly invoked by the user, supporting version pinning and offline verification. Maintained by Solismuchengxue, categorized under admin-security in SkillHub, with the GitHub repository currently having approximately 15 stars.

What Is This

One-line positioning: Swift Cycle governance skill adapter for DeepSeek Harness; user-invoked, version-pinned, offline-verifiable.

The adapter version is 0.1.1, and the upstream Swift Cycle is v1.2.0 (commit af3c5ddafba516c304613ea69081118fc234add7). The npm package name is dsh-plugin-swift-cycle, licensed under MIT. The complete governance rules are based on the locked upstream SKILL.md; this adapter’s README does not replicate the Skill content.

Core Capabilities

The Swift Cycle capabilities registered by the adapter with the Harness include:

  • Knowledge Promotion: Promoting long-term shared facts from local records to appropriate Git-managed assets.
  • State Separation: Separating independent engineering, experiments, quality, and release conclusions.
  • Governance Baseline: Recording a comparable current baseline before starting complex governance.
  • Commit Boundary Planning: Pre-dividing single-intent and verification boundaries for multi-commit work.
  • Source/Runtime Boundary: Separately verifying source code, artifacts, runtime, and actual consumers.

The invocation strategy is as follows. The adapter registers name = swift-cycle, modelInvocable = false, userInvocable = true. Swift Cycle does not enter the Skill catalog that the model can implicitly select; users must explicitly input:

/swift-cycle

Installation and Activation

For routine installation, use npm latest:

dsh plugin --profile web add dsh-plugin-swift-cycle

When a fixed, replayable installation identity is needed, specify the version:

dsh plugin --profile web add dsh-plugin-swift-cycle@0.1.1

npm fixed versions are immutable. To install the same version directly from GitHub, use the full 40-character commit corresponding to v0.1.1:

dsh plugin --profile web add "github:Solismuchengxue/dsh_plugin_swift_cycle#d44bee70c109bb1d772d26ee790d6de9aadce9cc"

Before installation or profile changes, check the synthetic configuration:

dsh --profile web --dump-config

The GitHub v0.1.0 fixed commit and npm 0.1.1 have both been installed, loaded, and smoke-tested with read-only invocations in the same real Web profile. Installation in other profiles still requires separate user authorization. The installation identities and verification boundaries for each version are based on the corresponding GitHub Release v0.1.1; do not use the unfixed default branch for replayable installations.

Typical Usage

After installation, explicitly invoke in DSH conversations:

/swift-cycle

If maintainers need to locally verify the adapter’s consistency with the upstream payload, Node.js 20 or higher is required. This package has no runtime dependencies and does not require executing installation lifecycle scripts:

npm test
npm run verify:upstream
npm run pack:dry-run

You can also explicitly provide a Swift Cycle checkout for read-only payload comparison:

node scripts/verify-upstream.mjs --source "<path-to-swift-cycle-skill-directory>"

The adapter does not access the network, read credentials, or modify user-level Skill directories during loading and runtime. When installed via npm or GitHub, the distribution tool still needs internet access to fetch the user-specified pinned version.

Applicable Scenarios and Notes

Who Is This For

  • Developers who need to perform project governance, state separation, and commit boundary planning in DSH according to Swift Cycle rules.
  • Teams that want Skill versions to be pinnable, payloads to be verifiable offline, and invocations to require explicit user triggering.

Important Notes

  • The plugin runs with the current dsh process permissions; before installation, you should review the source code and MIT license, and understand its governance boundaries.
  • According to the locked DeepSeek Harness Skill Registry rules, project-level entries with the same name can override this adapter’s Runtime registration; Runtime registration may shadow user-level entries with the same name at the same layer. This adapter does not delete or rewrite shadowed Skills.
  • The verification conclusions documented in the repository cover source code, candidate artifacts, isolated Harness Runtime, and partial real Web consumer smoke tests, and do not represent validation for other projects, write workflows, or production governance.

The DSH ecosystem philosophy is “everything is a plugin.” SkillHub is an independent community directory site, with no official affiliation to DeepSeek / High-Flyer.

Conclusion

dsh_plugin_swift_cycle integrates Swift Cycle v1.2.0 into DSH in a version-locked, user-explicitly-invoked, offline-verifiable manner, suitable for structured project governance in admin-security scenarios.

  • SkillHub Directory Page: https://www.skillhub.cn/plugins/Solismuchengxue/dsh_plugin_swift_cycle
  • GitHub Repository: https://github.com/Solismuchengxue/dsh_plugin_swift_cycle