Archify DSH Plugin
A DeepSeek Harness integration that runs Archify against a codebase and produces structured JSON plus an interactive HTML architecture map.
Project overview
Archify DSH Plugin is a DSH plugin built around a DeepSeek Harness integration that runs Archify against a codebase and produces structured JSON plus an interactive HTML architecture map. Its value is practical: scan repository structure and generate architecture maps are available from one documented project, while the repository remains inspectable before it is added to an agent workflow.
Core capabilities
Scan repository structure
Scan repository structure is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.
Generate architecture maps
Generate architecture maps is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.
Produce machine-readable results
Produce machine-readable results is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.
Invoke the skill from DSH
Invoke the skill from DSH is documented in the repository README or its component instructions. Review the linked source for current behavior and requirements.
Installation and usage
Set up Archify DSH Plugin from its public GitHub instructions, keep the initial permission scope small, and verify it with a low-risk task before regular use.
Let an AI Agent install it
Send this prompt to Codex, Claude Code, or another AI agent that can work with your local environment.
Help me set up Archify DSH Plugin.
Project URL: https://github.com/tt-a1i/archify
Component path: integrations/deepseek-harness
Read the repository README and license first. Confirm the current host, prerequisites, destination paths, and permissions. Follow the repository's documented method, keep credentials out of files and logs, and start with the least-privilege or read-only option where available. Afterward, run a small verification and report the exact changes, commands, configuration path, and result. Ask before overwriting files or requesting broader access.- DeepSeek Harness is installed
- The target repository is readable by the current user
dsh plugin --profile web add @tt-a1i/archify-dsh@0.1.0- 1Review prerequisites and scope
Read the README, confirm the target host, and prepare these prerequisites: DeepSeek Harness is installed; The target repository is readable by the current user. Check destination paths and permissions before making changes.
- 2Apply the documented setup
Run the documented command: dsh plugin --profile web add @tt-a1i/archify-dsh@0.1.0
- 3Verify with a small task
Run dsh --profile default --dump-config or the matching profile command, confirm that Archify DSH Plugin is loaded, then invoke its smallest documented action.
Run dsh --profile default --dump-config or the matching profile command, confirm that Archify DSH Plugin is loaded, then invoke its smallest documented action.
- Static architecture maps do not replace runtime analysis
- Large repositories may require scope control
Use cases
Understand an unfamiliar codebase
Understand an unfamiliar codebase is a practical fit when the repository's documented prerequisites and permission model match the current environment.
Prepare an architecture map for refactoring
Prepare an architecture map for refactoring is a practical fit when the repository's documented prerequisites and permission model match the current environment.
Create a repository overview for review
Create a repository overview for review is a practical fit when the repository's documented prerequisites and permission model match the current environment.
Assessment
This assessment is based on the repository README, component documentation, license, and maintenance metadata. Outputs are useful to both people and agents; No extra service or account is required after installation. The main trade-offs are also clear: Static architecture maps do not replace runtime analysis; Large repositories may require scope control. No local installation or functional test was claimed during cataloging.
Why it may be useful
- Outputs are useful to both people and agents
- No extra service or account is required after installation
What to know first
- Static architecture maps do not replace runtime analysis
- Large repositories may require scope control
README
Archify DSH Plugin
Overview
A DeepSeek Harness integration that runs Archify against a codebase and produces structured JSON plus an interactive HTML architecture map. A DeepSeek Harness integration that runs Archify against a codebase and produces structured JSON plus an interactive HTML architecture map.
Getting started
- Set up Archify DSH Plugin from its public GitHub instructions, keep the initial permission scope small, and verify it with a low-risk task before regular use.
- The repository describes Archify DSH Plugin as a DeepSeek Harness integration that runs Archify against a codebase and produces structured JSON plus an interactive HTML architecture map.
- Its main capabilities include scan repository structure, generate architecture maps, produce machine-readable results, invoke the skill from dsh. The documented facts include json and html output, repository structure analysis, no background service, no credentials required.
- Run dsh --profile default --dump-config or the matching profile command, confirm that Archify DSH Plugin is loaded, then invoke its smallest documented action.
Configuration
dsh plugin --profile web add @tt-a1i/archify-dsh@0.1.0