nntrivi2001
b7c573f8d9
The repo root already IS the `ccam` plugin root (`"source": "./"`), so the conventional `skills/` dir at the root is the plugin's skills dir — while `.claude/skills/` only loaded for a session whose cwd was inside this checkout. That is useless for a lane working in another repo, which is why `ccam skills install` existed at all. Move all seven skills to `skills/`: they now reach every plugin user as `/ccam:<name>` (bare `/<name>` as an alias). `ccam skills install` stays as the fallback for a plain checkout without the plugin, sourcing from the new path. Agents deliberately do NOT move. A plugin agent is addressed as `ccam:qc-local`, which would break the `subagent_type: qc-local` references in ship-feature-lane; `ccam lanes agents install` keeps writing them into the lane's own `.claude/agents/`, the highest-priority agent source. MCP was already plugin-shipped via `plugins/ccam/.mcp.json`. Mechanical fallout: ~115 source files carry a doc-comment pointer to `.claude/skills/file-headers/`, repointed to `skills/file-headers/`. The generic Claude Code config-surface examples in openapi/cc-config (`.claude/ skills/code-reviewer`) describe any user's layout and are left alone. Also fixes the two file-headers scripts, whose `ROOT=` climbed four levels from `.claude/skills/file-headers/scripts/` and would have escaped the repo from the new depth — it scanned sibling projects until corrected to three. npm run test:server (1160 pass), test:client (422 pass), mcp:typecheck, mcp:build + mcp:check-build all green.
37 lines
1.6 KiB
JavaScript
37 lines
1.6 KiB
JavaScript
/**
|
|
* @file Installs skills/ship-feature-lane/ into ~/.claude/skills/, so
|
|
* /ship-feature-lane is discoverable from a session running inside any
|
|
* lane's own working directory. This is the FALLBACK path for a plain
|
|
* checkout: the skill also ships with the `ccam` plugin (the repo root IS
|
|
* the plugin root, so `skills/` is the plugin's skills dir), where it is
|
|
* already global as `/ccam:ship-feature-lane`. Installing it here just
|
|
* restores the bare `/ship-feature-lane` name for people who do not run the
|
|
* plugin. Shared by bin/ccam.js's `ccam skills install` CLI and the
|
|
* POST /api/skills/install route, so there is exactly one copy of this
|
|
* logic. Pure filesystem action.
|
|
* @author Nguyễn Ngọc Trí Vĩ <vinnt@smartgift.vn>
|
|
*/
|
|
|
|
const fs = require("node:fs");
|
|
const os = require("node:os");
|
|
const path = require("node:path");
|
|
|
|
/**
|
|
* @param {{repoRoot: string}} options - `repoRoot` is this checkout's own
|
|
* root (bin/ccam.js already computes this as `REPO_ROOT`; the server
|
|
* computes its own equivalent — see the route for how).
|
|
* @returns {{installed: true, path: string}}
|
|
*/
|
|
function installShipFeatureLaneSkill({ repoRoot }) {
|
|
const src = path.join(repoRoot, "skills", "ship-feature-lane");
|
|
if (!fs.existsSync(src)) {
|
|
throw Object.assign(new Error(`not found: ${src}`), { code: "ENOSKILLSRC" });
|
|
}
|
|
const dest = path.join(os.homedir(), ".claude", "skills", "ship-feature-lane");
|
|
fs.mkdirSync(path.dirname(dest), { recursive: true });
|
|
fs.cpSync(src, dest, { recursive: true, force: true });
|
|
return { installed: true, path: dest };
|
|
}
|
|
|
|
module.exports = { installShipFeatureLaneSkill };
|