메뉴
End-to-end installer test for a contributor: builds a local tarball from installer/, runs the installer via npx for the chosen harness, bootstraps the plugin, and verifies via doctor and sha256 manifest check. Use when asked to "test the installer", "build and install the harness", or "verify the install".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use this skill once you are aligned on a project and ready to start. Typically this is invoked directly by the user after /rad-brainstorm has completed and the Requirements doc is approved. It is the reference for how to run the planning pipeline and author the Master Plan.
Drive the release flow locally — context, version reconcile, build, validate, CHANGELOG, commit, sync plugins to the marketplace, and tag/push (which triggers the CI npm publish + GitHub Release), then a post-release dev bump.
Use this skill if you are a main agent, coder agent and have this skill assigned. It is the reference for how to perform source-control operations like creating commits, opening pull requests, and creating or cleaning up worktrees for a project.
Use this skill if you're a main agent orchestrator executing a rad-orchestration project. It is the reference for how to run the pipeline, signal events, execute actions, and manage the overall flow of a project. Typically, you are guided to using this skill when /rad-execute is invoked, but you may read it if you need to refresh your memory due to compaction during an execution.
Rebuild the standard installer and reinstall one harness (claude, copilot-vscode, or copilot-cli) locally — build the rad-orc tarball, stop the UI, uninstall then reinstall the harness, restart the UI. Use to dogfood canonical harness-files/ agent and skill edits into ~/.claude or ~/.copilot.
Use this skill if you are a main agent who is helping to author planning documents (Requirements or Master Plan). This is triggered by the pipeline or by a brainstorm handoff. It is the reference for how to author planning documents in the rad-orc workflow.
| name | rad-build-harness |
| description | End-to-end installer test for a contributor: builds a local tarball from installer/, runs the installer via npx for the chosen harness, bootstraps the plugin, and verifies via doctor and sha256 manifest check. Use when asked to "test the installer", "build and install the harness", or "verify the install". |
Where this fits. rad-build-harness is the quick contributor dogfood loop — pack, install, bootstrap, verify on a single harness. The comprehensive cross-cutting smoke is .agents/prompts/rad-test-release.prompt.md (legacy installer) and .agents/prompts/rad-test-plugin-release.prompt.md (Claude plugin). Use this skill when you want a fast feedback cycle on a build change; use the release prompts for go/no-go decisions.
Run the real installer end-to-end from local source. This skill selects a harness, builds the canonical adapter sources, packs the installer into a tarball, runs the wizard non-interactively via npx, bootstraps the plugin (with --force to defeat the version-equal short-circuit on repeat runs), and verifies the result.
~/.radorc/projects/ is never touched at any point in this workflow — existing user projects survive unchanged.
doctor reports a clean state after a fresh or upgraded install.Use AskUserQuestion with these options:
| Label | Value |
|---|---|
| Claude Code | claude |
| GitHub Copilot in VS Code | copilot-vscode |
| GitHub Copilot CLI | copilot-cli |
Record the answer as {harness}.
git rev-parse --show-toplevel
Use the result as {repoRoot} for every subsequent command.
cd {repoRoot}/installer && npm pack
Note the generated tarball filename — something like rad-orchestration-X.Y.Z.tgz. Store it as {tarball}. The full absolute path is {repoRoot}/installer/{tarball}.
npx {repoRoot}/installer/{tarball} --version
Tests the wizard surface: the single harness-question prompt and the canonical orchestration.yml write.
npx {repoRoot}/installer/{tarball} --yes --harness {harness}
Expected: installer completes without interactive prompts and exits with code 0.
~/.radorc/projects/is not touched.
Tests the force-bootstrap path: defeats the version-equal short-circuit so a repeat test on the same version still re-runs the bootstrap.
Locate the bundled plugin root for the harness. The plugin payload ships at {repoRoot}/installer/src/{bundleDir}/ where bundleDir matches the harness:
| Harness | Bundle directory |
|---|---|
claude | installer/src/claude/ |
copilot-vscode | installer/src/copilot-vscode/ |
copilot-cli | installer/src/copilot-cli/ |
Run plugin-bootstrap with --force to defeat the version-equal short-circuit:
npx {repoRoot}/installer/{tarball} plugin-bootstrap --force --harness {harness} --plugin-root {repoRoot}/installer/src/{bundleDir}
--forceensures the bootstrap runs even when the delivering version equals the installed version. This is required on repeat test runs.
Run all three checks and report any failure:
npx {repoRoot}/installer/{tarball} --version
npx {repoRoot}/installer/{tarball} doctor
sha256 manifest check: The manifest catalog is written into the bundled plugin payload during npm pack (via the prepack lifecycle hook). Verify that the manifest file for the tested version exists and that every entry carries a sha256 field.
The manifest path is:
{repoRoot}/installer/src/{bundleDir}/manifests/v{version}.json
Open the file and confirm:
sha256 field with a non-empty value.Report:
doctor passed or flagged issues.cd {repoRoot}/installer && Remove-Item -Force {tarball}
The global install extracts the package at install time and no longer references the file. Delete it to keep the working tree clean.