[PR #7450] [CLOSED] docs(clients): install the Harness skill through its own client #7844

Closed
opened 2026-11-05 01:48:04 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/7450
Author: @XiaoBinGan
Created: 10/27/2026
Status: ❌ Closed

Base: main ← Head: docs/dsh-skill-client


📝 Commits (1)

  • 7f1e452 docs(clients): install the Harness skill through its own client

📊 Changes

1 file changed (+4 additions, -3 deletions)

View changed files

📝 docs/client-configuration.md (+4 -3)

📄 Description

Summary

The DeepSeek Harness section tells readers to run rea setup --skill --dry-run / --skill --yes and says the skill lands in ~/.agents/skills. With --skill-client dsh the skill goes to the client's own root instead ($DSH_AGENTS_HOME/skills, defaulting to ~/.agents/skills), which is what the DSH client resolution in src/application/SupportedClients.ts selects.

Refs #4402 — that discussion chose the DSH skill root; this makes the setup instruction name the flag that selects it.

Problem and expected behavior

docs/client-configuration.md, DeepSeek Harness section:

Run rea setup --skill --dry-run, review the destination, then rea setup --skill --yes to install the workflow in ~/.agents/skills ($DSH_AGENTS_HOME/skills when configured)

Two problems with that as a DSH instruction:

  • The command omits --skill-client dsh, so it installs into the shared root rather than the client's own root.
  • The parenthetical implies the shared path is always the destination, when for DSH it is the default of a different root.

docs/installation.md already states the rule the flag implements: "Selecting the skill without a client uses ~/.agents/skills". So setup without a client is the shared path, and DSH needs the client selected.

Change and scope

One sentence: the two commands gain --skill-client dsh, and the destination is described as $DSH_AGENTS_HOME/skills defaulting to ~/.agents/skills. Nothing else on the page changes.

Contract and boundary impact

Documentation only. No CLI, MCP/tool-catalog, provider, artifact, or generated-metadata change; docs:check passes unchanged.

Expected effects:

  • Documentation or usability only; no target interaction.

Evidence and regression coverage

  • src/application/SupportedClients.ts — clientSkillDirectories returns ["shared"] when no client is selected and clientIds otherwise; sharedDirectory is appendCallerPath(home, ".agents/skills", platform).
  • docs/installation.md:160 — "Selecting the skill without a client uses ~/.agents/skills", which is the shared path the old sentence attributes to DSH unconditionally.
  • No tests added; prose only, and the client-resolution suites already cover which root each client selects.

Validation performed

  • Read clientSkillDirectories and sharedDirectory in src/application/SupportedClients.ts
  • npx oxfmt --check docs/client-configuration.md — exit 0
  • npm run docs:check — exit 0, 9 tests passed

Compatibility, safety, and release

No breaking change, migration step, package or release metadata impact, or security review. Documentation only.

Author readiness

Human owner: @XiaoBinGan

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/7450 **Author:** [@XiaoBinGan](https://github.com/XiaoBinGan) **Created:** 10/27/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `docs/dsh-skill-client` --- ### 📝 Commits (1) - [`7f1e452`](https://github.com/morluto/rea/commit/7f1e4529a529528761fc68fec6fb35b40505ec39) docs(clients): install the Harness skill through its own client ### 📊 Changes **1 file changed** (+4 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `docs/client-configuration.md` (+4 -3) </details> ### 📄 Description ## Summary The DeepSeek Harness section tells readers to run `rea setup --skill --dry-run` / `--skill --yes` and says the skill lands in `~/.agents/skills`. With `--skill-client dsh` the skill goes to the client's own root instead (`$DSH_AGENTS_HOME/skills`, defaulting to `~/.agents/skills`), which is what the DSH client resolution in `src/application/SupportedClients.ts` selects. Refs #4402 — that discussion chose the DSH skill root; this makes the setup instruction name the flag that selects it. ## Problem and expected behavior `docs/client-configuration.md`, DeepSeek Harness section: > Run `rea setup --skill --dry-run`, review the destination, then `rea setup --skill --yes` to install the workflow in `~/.agents/skills` (`$DSH_AGENTS_HOME/skills` when configured) Two problems with that as a DSH instruction: - The command omits `--skill-client dsh`, so it installs into the shared root rather than the client's own root. - The parenthetical implies the shared path is always the destination, when for DSH it is the default of a different root. `docs/installation.md` already states the rule the flag implements: "Selecting the skill without a client uses `~/.agents/skills`". So setup without a client is the shared path, and DSH needs the client selected. ## Change and scope One sentence: the two commands gain `--skill-client dsh`, and the destination is described as `$DSH_AGENTS_HOME/skills` defaulting to `~/.agents/skills`. Nothing else on the page changes. ## Contract and boundary impact Documentation only. No CLI, MCP/tool-catalog, provider, artifact, or generated-metadata change; `docs:check` passes unchanged. Expected effects: - [x] Documentation or usability only; no target interaction. ## Evidence and regression coverage - `src/application/SupportedClients.ts` — `clientSkillDirectories` returns `["shared"]` when no client is selected and `clientIds` otherwise; `sharedDirectory` is `appendCallerPath(home, ".agents/skills", platform)`. - `docs/installation.md:160` — "Selecting the skill without a client uses `~/.agents/skills`", which is the shared path the old sentence attributes to DSH unconditionally. - No tests added; prose only, and the client-resolution suites already cover which root each client selects. ## Validation performed - Read `clientSkillDirectories` and `sharedDirectory` in `src/application/SupportedClients.ts` - `npx oxfmt --check docs/client-configuration.md` — exit 0 - `npm run docs:check` — exit 0, 9 tests passed ## Compatibility, safety, and release No breaking change, migration step, package or release metadata impact, or security review. Documentation only. ## Author readiness Human owner: @XiaoBinGan - [x] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [x] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [x] I declare this PR ready for initial maintainer review. ## Before merge - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-05 01:48:04 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7844
No description provided.