hitkeep-workspace

Name: hitkeep-workspace
Author: PascaleBeier

72stars6forks

How to install hitkeep-workspace?

pascalebeier/hitkeep/hitkeep-workspace

$npx -y skills add PascaleBeier/hitkeep --skill hitkeep-workspace

Installs into the current project.

Summary

Operate HitKeep safely in isolated Git worktrees. Use when inspecting workspace state, resolving ports or URLs, starting or stopping development services, coordinating concurrent agents or QA runs, reusing active runs, reading bounded logs, or preparing a secret-free handoff.

Files · 1

View on GitHub

SKILL.md

1	# HitKeep Workspace
2
3	Treat `AGENTS.md` as policy and `hk` as the live workspace authority. Git worktree creation and deletion remain external responsibilities. Never infer workspace identity from the directory name or branch.
4
5	## Inspect First
6
7	Use these local developer MCP operations whenever they are callable:
8
9	- `hk_workspace_status` for the current worktree, ports, URLs, and change summary.
10	- `hk_workspace_list` to see isolated HitKeep workspaces.
11	- `hk_workspace_handoff` for compact continuation context.
12	- `hk_run_status` and `hk_logs_tail` for asynchronous work.
13	- `hk_run_list` to reuse or inspect bounded recent work before starting another run.
14	- `hk_dev_start`, `hk_dev_status`, `hk_dev_logs`, and `hk_dev_stop` for this worktree's container-only development session.
15	- `hk_screenshot` for batched, workspace-managed visual-QA artifacts from the active local session.
16	- `hk_run_cancel` for one validated active run.
17
18	Do not invoke equivalent workspace or run CLI commands unless the relevant MCP tool is not callable, the registration, startup, root-routing, or task-reload blocker has been reported, and the user has given explicit user approval. After approval, discover the equivalent command through `./hk catalog commands --output json`, request `--output json`, and add `--detach` for action parity. Do not parse terminal prose.
19
20	Always use the workspace ID, Compose project, paths, ports, URLs, development event cursors, and finite-operation run IDs returned by `hk`. Verify an envelope's workspace ID before using a cursor or run ID. Never assume conventional ports are free or share mutable state between worktrees.
21
22	## Operate
23
24	1. Inspect status, the development session, and active finite runs before setup, browser work, e2e, or QA. Reuse equivalent active work rather than duplicating it.
25	2. Query the live variant catalog, then start the container-only development session only when the task needs services.
26	3. Development start streams until ready or failed and requires no session ID. Finite operations return run IDs and are polled with reasonable intervals. Do not treat client disconnect or a slow call as failure.
27	4. Read bounded log tails for diagnosis. Carry `next_cursor` into subsequent development or run reads so repeated polling does not reload old output. Use returned artifact paths for complete local diagnostics instead of loading full logs into context.
28	5. Stop development with the workspace-scoped stop operation. Cancelling a development log observer never stops services; finite run cancellation still targets one validated run ID.
29	6. Before handoff, refresh status and request handoff context. Report workspace ID, active runs, usable URLs, changed-path summary, failures, and the next safe action.
30
31	Do not run `git clean`, remove unmanaged files, delete worktrees, expose secrets, copy mutable state between workspaces, or manually reserve ports. Reject paths that resolve outside the selected worktree, including symlink escapes.

People who liked this also viewed

6 picks

Type

hitkeep-workspace

72stars6forks

View on GitHub

How to install hitkeep-workspace?

pascalebeier/hitkeep/hitkeep-workspace

$npx -y skills add PascaleBeier/hitkeep --skill hitkeep-workspace

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# HitKeep Workspace
2
3	Treat `AGENTS.md` as policy and `hk` as the live workspace authority. Git worktree creation and deletion remain external responsibilities. Never infer workspace identity from the directory name or branch.
4
5	## Inspect First
6
7	Use these local developer MCP operations whenever they are callable:
8
9	- `hk_workspace_status` for the current worktree, ports, URLs, and change summary.
10	- `hk_workspace_list` to see isolated HitKeep workspaces.
11	- `hk_workspace_handoff` for compact continuation context.
12	- `hk_run_status` and `hk_logs_tail` for asynchronous work.
13	- `hk_run_list` to reuse or inspect bounded recent work before starting another run.
14	- `hk_dev_start`, `hk_dev_status`, `hk_dev_logs`, and `hk_dev_stop` for this worktree's container-only development session.
15	- `hk_screenshot` for batched, workspace-managed visual-QA artifacts from the active local session.
16	- `hk_run_cancel` for one validated active run.
17
18	Do not invoke equivalent workspace or run CLI commands unless the relevant MCP tool is not callable, the registration, startup, root-routing, or task-reload blocker has been reported, and the user has given explicit user approval. After approval, discover the equivalent command through `./hk catalog commands --output json`, request `--output json`, and add `--detach` for action parity. Do not parse terminal prose.
19
20	Always use the workspace ID, Compose project, paths, ports, URLs, development event cursors, and finite-operation run IDs returned by `hk`. Verify an envelope's workspace ID before using a cursor or run ID. Never assume conventional ports are free or share mutable state between worktrees.
21
22	## Operate
23
24	1. Inspect status, the development session, and active finite runs before setup, browser work, e2e, or QA. Reuse equivalent active work rather than duplicating it.
25	2. Query the live variant catalog, then start the container-only development session only when the task needs services.
26	3. Development start streams until ready or failed and requires no session ID. Finite operations return run IDs and are polled with reasonable intervals. Do not treat client disconnect or a slow call as failure.
27	4. Read bounded log tails for diagnosis. Carry `next_cursor` into subsequent development or run reads so repeated polling does not reload old output. Use returned artifact paths for complete local diagnostics instead of loading full logs into context.
28	5. Stop development with the workspace-scoped stop operation. Cancelling a development log observer never stops services; finite run cancellation still targets one validated run ID.
29	6. Before handoff, refresh status and request handoff context. Report workspace ID, active runs, usable URLs, changed-path summary, failures, and the next safe action.
30
31	Do not run `git clean`, remove unmanaged files, delete worktrees, expose secrets, copy mutable state between workspaces, or manually reserve ports. Reject paths that resolve outside the selected worktree, including symlink escapes.

People who liked this also viewed

6 picks

Type