dsh-archify

🚀 Usage

Ask the agent to load the skill by name:

Use the archify skill to map this repository's runtime architecture.
Show 8–12 core components, one primary path, external dependencies, and trust boundaries.
Put supporting detail in cards instead of adding more edges.
After delivery, return the exact workspace paths of the specification JSON and the HTML artifact.

Uninstall:

dsh plugin --profile  remove dsh-archify

Produced Files limitation: files created by shell commands do not automatically appear in the Web Produced Files strip — ask the agent to return the exact workspace paths of the specification JSON and the HTML artifact, then open them from the workspace (same as the official upstream DSH package).

Security posture: no telemetry, network client, credentials handling, or background service; no install / postinstall / preinstall lifecycle hooks (only prepare stages the skill files).

Port notes (vs upstream tt-a1i/archify @ archify-dsh-v0.1.0)

Byte-identical, diff-verifiable: archify/ (SKILL.md, renderers, schemas, bin, examples, recipes, references, assets, delta, scripts, test) and the root examples/ are upstream files.

Verify it yourself — don't take our word — THIRD_PARTY_NOTICES.md pins the upstream release tag, commit, and per-file SHA-256 with copy-paste compare commands; test/zero-regression.test.mjs re-checks the pins on every npm test.

Adaptations (official @tt-a1i/archify-dsh@0.1.0 → dsh-archify): package name and resolution path; added prepare (upstream ships a prebuilt tarball; a git install must stage skills/ itself); upstream repo-root website/release files (docs/, README_EN.md, README_ZH.md, benchmarks/, .github/, …) are not part of the skill payload and were not ported.

Known limitation: skill copy is English — that is upstream's original text, kept verbatim.