Git & Version Control

What it is — A PiUI-style diff viewer that replaces diff rendering for write/edit tool calls.

Who it is for — When using write/edit tool calls in DeepSeek Harness, this plugin is suitable to install. Users who only want to use the official default diff experience can choose other plugins.

Watch out — Sandbox test passed: successfully installed in a new profile and registered to the harness. No issues found from static checks. No obvious pitfalls discovered.

The verdict — I would install it because it is a pure plugin that restores the official line upon uninstall.

What it is — Scans React, TypeScript, JavaScript, and Vue 3 code to simulate user personas, detect UX issues, and provide concrete suggestions.

Who it is for — When developing a React application with DeepSeek Harness and needing UX simulation capabilities, this plugin is suitable. If your project uses Svelte or Vue 2 frameworks, you do not need to install this plugin, as it does not support analysis for those languages.

Watch out — Sandbox test passed successfully with installation and registration in a fresh profile and no obvious issues found. It can obtain browser evidence when rendered page support is available, but relies only on static evidence without browser environment.

The verdict — I would install it because it automatically runs the walkthrough after file edits and provides locatable UX optimization suggestions.

What it is — Integrates tools for GitHub and other developer ecosystems.

Who it is for — When using the DeepSeek Harness agent to handle open source repository issues. If your workflow only involves local tools, it is not suitable.

Watch out — Sandbox testing passed; successfully installed in a fresh profile and registered into the harness. No obvious issues found.

The verdict — I would install it because it integrates queries without an API key.

What it is — Tracks write/edit tool calls in DeepSeek Harness sessions and renders line-level diffs with customizable colors.

Who it is for — If you use DeepSeek Harness web profile to perform file editing and need real-time diff preview, this plugin is suitable for you. If you don't use subagent aggregation, you can skip installing this plugin.

Watch out — Sandbox test passed on a fresh profile. No obvious issues found. Review records persist to disk and colors persist in local storage.

The verdict — I would install it because it offers session isolation and live SSE updates, but only if the number of operations per file stays under 100.

What it is — DSH plugin fixes git commit authors to the environment's own identity.

Who it is for — DSH agent sessions performing git commits need this to ensure correct author identity. Users who perform git commits only in ordinary terminal clients do not need this plugin.

Watch out — After installation, restart the DSH process. Sandbox test passed with successful registration in fresh profile. No obvious issues found.

The verdict — I would install it because it overrides git config settings via env vars to ensure consistent authors for DSH commits and sandbox tests confirm it works.

What it is — Provides Git worktree isolation and delivery for DeepSeek Harness sessions.

Who it is for — When you need to isolate code modifications in DeepSeek Harness sessions. Users who do not perform git version control changes are not suitable for it.

Watch out — Sandbox test passed: installed in new profile and registered into profile. No obvious issues found.

The verdict — I would install it because it provides ready-for-review lifecycle management, but only if the agent uses model tools.

What it is — Integrates AtomGit skills, ag CLI, and platform-hosted MCP tools into DeepSeek Harness.

Who it is for — DeepSeek Harness users who need to manage AtomGit code repositories through issue planning, PR implementation, review, and merge are suitable for installation. Users who do not use any platform integrations or shell commands are not appropriate for this plugin.

Watch out — Sandbox test passed in a new profile with registration by harness. From source install, need to manually allow the build script. No obvious issues found.

The verdict — I would install it because all three modules share one unified AtomGit PAT with no separate token setup required.

What it is — This plugin performs GitHub login using device flow inside a window and syncs the token to the gh CLI.

Who it is for — If you use DeepSeek Harness profile and need GitHub CLI access without terminal interaction, this fits. If you do not need GitHub CLI integration and only use browser-based GitHub login, this is unnecessary.

Watch out — It executes shell commands per static checks. Sandbox testing passed after installing in a new profile and registering it with Harness. No obvious issues found.

The verdict — I would install it because it allows GitHub login inside a window and syncs the token to the gh CLI.

What it is — dsh-github-skills provides DeepSeek Harness with GitHub workflow skills for PR triage, review feedback, CI diagnosis, and safe draft-PR publishing.

Who it is for — When using DeepSeek Harness for GitHub-related software development, dsh-github-skills can help with PR triage, review feedback, CI diagnosis, and safe publishing if your setup requires GitHub integration. For developers whose work is entirely local without GitHub repository connections, this plugin offers no benefit.

Watch out — Sandbox test passed with successful installation and registration in a fresh profile. No obvious issues were found.

The verdict — I would install it because it provides a layer on top of DSH's existing GitHub capabilities with gh/git fallbacks, but only if your DSH sessions involve GitHub PR triage and CI diagnosis.

What it is — dsh-revdiff is a DeepSeek Harness plugin that allows interactive Git diff review in the terminal with structured annotations returned to the Agent session.

Who it is for — Users reviewing tracked working-tree changes in DeepSeek Harness who want structured annotations sent back to the Agent session are suitable for installing this plugin. Users not using the Harness interactive terminal can skip installing this plugin.

Watch out — Sandbox testing shows the plugin installs but pnpm blocks its build script, preventing Harness registration. Users must manually allow the build script to complete the process. No other issues were found in static checks.

The verdict — I would install it because it keeps diff review connected to the Agent's durable session instead of breaking the link with an external tool, but I must manually allow the build script first.

What it is — Provides secure Git tools for models including status, diff, log, commit, and branch.

Who it is for — When the model needs to manage a code repository in a development session. Not suitable for sessions requiring stronger isolation.

Watch out — Sandbox test passed: installed in a new profile and registered by Harness, running normally. Git tools run as host process without fs-sandbox isolation. Commit requires git user.name and user.email configured in the repo.

The verdict — I would install it because it makes git calls safe and passed sandbox test, but with the premise that the session allows host-level git execution.

What it is — Integrates git CLI into DeepSeek Harness for Conventional Commits enforcement, changelog generation, PR summaries and branch pushes.

Who it is for — When developing code with DeepSeek Harness and needing to enforce Conventional Commits along with auto PR summaries. Not suitable for users who rely on platform APIs or tokens.

Watch out — Installed from GitHub source code. Successfully tested in a fresh profile and registered by harness. No obvious issues found.

The verdict — I would install it because it enables git workflow without needing platform APIs or tokens.

What it is — dsh-github-release-radar plugin provides four GitHub API tools for DeepSeek Harness agents: github_releases, github_repo, github_search, and github_repo_tags. These tools allow direct calls to GitHub REST API for public repository data without API key.

Who it is for — When using DeepSeek Harness agents to analyze open-source projects, this plugin exposes tools for accessing releases, repository overview, search, and tags. If your agent workflow does not involve external GitHub repository queries, you may choose not to install this plugin.

Watch out — Sandbox testing showed that the plugin can be loaded into the sandbox but its build script is blocked by pnpm; users need to manually allow the build for github:zoahdev/dsh-github-release-radar to complete harness registration. The plugin supports optional githubToken configuration to increase the anonymous 60 requests per hour limit. No obvious runtime issues were found.

The verdict — I would not install it because manual build allowance is required to complete registration, and there is no evidence of its long-term stability.

What it is — PR evaluation advisor that assesses the success probability of PR submissions based on historical patterns and provides actionable suggestions.

Who it is for — Developers submitting PRs to other open-source repositories can use this tool to assess the success probability before opening them. Individuals focused only on maintaining their own repository can choose not to install it.

Watch out — Installation from GitHub source requires manually allowing the build script to execute. The sandbox test confirmed it runs normally after installation in a fresh profile and registration.

The verdict — I would install it because it supports structured monitoring of outbound PRs across repositories, but only if you are in a Python environment.

What it is — DeepSeek Harness plugin provides task-isolated Git workspaces with full lifecycle management.

Who it is for — When the model processes multiple tasks in parallel, this plugin automatically creates isolated Git workspaces to prevent main workspace pollution. If you prefer simple single-task editing without Git branch isolation, you can choose not to install this plugin.

Watch out — Sandbox test passed: installation in a new profile and successful registration by harness. The plugin will execute shell commands. No obvious pitfalls found.

The verdict — I would install it because it enables zero manual git operations for parallel tasks, but only if using a Node 21 or higher environment.

What it is — The github-explore plugin wraps gh CLI to convert GitHub searches into structured, deduplicated, relevance-scored outputs, supporting multi-axis exploration and repo summaries.

Who it is for — Researchers using DeepSeek Harness to explore multi-agent collaboration repos benefit from this plugin's multi-dimensional search. Users seeking minimal output complexity may find it unnecessary.

Watch out — Installation requires npm and gh CLI setup. Sandbox testing passed with no obvious issues.

The verdict — I would install it because it structures gh search results with relevance scoring to reduce context window usage.

What it is — It adds a dedicated read-only Git Graph view beside Chat and Trajectory in the DeepSeek Harness web interface.

Who it is for — If you need to check the workspace's Git history in DeepSeek Harness, this plugin is suitable. If you need to modify Git repository data, this plugin is not suitable.

Watch out — Sandbox testing passed. It was installed in a new profile and registered into the profile. No obvious issues were found.

The verdict — I would install it because it displays an empty state instead of an error when the current directory is not a Git repository or the repository has no commits yet.

What it is — dsh-gitflow supplies approval-gated Git status, diff, log, commit, branch tools, plus optional checkpoint functionality.

Who it is for — If your DeepSeek Harness agent tasks involve Git operations such as code review or branch management, this plugin integrates them safely via the approval mechanism. If you prefer not to execute shell commands or avoid installing from source, it does not fit.

Watch out — Sandbox testing revealed that the build script is blocked by pnpm, requiring manual allowance for github:lonelymoon87/dsh-gitflow to complete registration. It executes shell commands but follows a safety model that prevents implicit git add/reset operations. No other runtime issues were observed.

The verdict — I would install it if my agent needs Git integration and can manually allow the build, because it offers safe integration of Git tools rather than direct commands.