disconnect-board

Remove the board connection from the current workspace via write-config.

24|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/yves-s/just-ship --skill disconnect-board
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: disconnect-board
Source: https://github.com/yves-s/just-ship/tree/main/skills/disconnect-board
Command: npx skills add https://github.com/yves-s/just-ship --skill disconnect-board

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill removes the existing connection between Just Ship and its board, allowing the pipeline to operate without board events or status updates.

Core Features & Use Cases

  • Detaches the board from the current workspace.
  • Switches the pipeline to a CLI‑only mode for offline development.
  • Preserves the workspace ID so a later reconnect can restore the board link.

Quick Start

Run the disconnect‑board command to detach the board and enable CLI‑only operation.

Frequently Asked Questions about disconnect-board

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove a board integration and revert my workspace to CLI-only mode?

To remove a board integration and revert to CLI-only mode, you run the disconnect-board command. This executes a write-config script that deletes the board configuration from project.json, halting board event updates for the workspace.

Why does my pipeline still receive board status updates after I disconnect the board?

If board status updates continue after you disconnect the board, the write-config script may lack the necessary permissions to modify project.json. Ensure the script can successfully delete the board configuration to stop pipeline event updates.

Do I need to modify project.json manually to switch my pipeline to CLI-only operation?

You do not need to modify project.json manually to switch to CLI-only operation. The disconnect-board command automatically executes the write-config script to delete the board configuration and detach the board from the current workspace.

Will disconnecting the board delete my workspace ID?

Disconnecting the board will not delete your workspace ID. The process preserves the workspace ID specifically so you can restore the board link and reconnect the pipeline to board events at a later time.

When should I use a board disconnect command for my development pipeline?

You should use a board disconnect command when you need to switch your development pipeline to CLI-only mode for offline work. It detaches the board from the workspace, stopping event updates while preserving the underlying project configuration.