dsh-lens

Managing multiple Git repositories means facing the same set of questions over and over without a systematic way to answer them: where are the orchestration bottlenecks? Is the runtime policy wasting resources? Could sensitive data leak before or after going public? Could the project itself be packaged as a DSH plugin? dsh-lens bundles these scattered concerns into a set of structured, read-only workflows so a single pass produces traceable conclusions instead of manual file-by-file digging.

The plugin ships five workflows: repo-recon runs staged, read-only reconnaissance of a local Git project via parallel subagents; dsh-enhancement-analysis maps the orchestration pain points of any project onto DSH capabilities and emits a prioritized report; harness-runtime-optimizer diagnoses runtime-policy waste, designs controlled experiments, and evaluates policy changes; publish-screen screens a repository for sensitive information before or after making it public; dsh-plugin-potential assesses whether the functionality of a project could be packaged as a DSH plugin, evaluation only, never build.

Every workflow is strictly read-only: reports land in the dsh-scan/ directory under the analyzed project, the repository is never modified, and runtime policies are never changed automatically. This makes dsh-lens a natural fit for DSH users who need ongoing codebase health assessments, infrastructure engineers who own runtime policy, and teams that require a structured screening report during security and compliance reviews.