원클릭으로 Manus에서 모든 스킬 실행

workhorse-horsed-dev

스타3

포크1

업데이트2026년 3월 7일 10:54

Use when the user wants to modify the `horsed` server implementation itself, including SSH server behavior, setup flow, logging, IPC, SQLite schema, migrations, service startup logic, or server-side tests.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

uuhan

uuhan/workhorse

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Workhorse Horsed Dev

Overview

This skill is for changing horsed code, not just operating a deployed server. Use it when the task touches server-side actions, database schema, process lifecycle, logging, or setup behavior.

Code Map

../../horsed/src/main.rs: process model, CLI, daemon and foreground startup.
../../horsed/src/ssh/mod.rs: main SSH server on 2222 and action dispatch.
../../horsed/src/ssh/jobs.rs: in-memory job registry, bounded output buffers, and attach event stream.
../../horsed/src/ssh/setup.rs: first-user bootstrap server on 2223.
../../horsed/src/ssh/health.rs: health action and ulimit -n reporting.
../../horsed/src/logger/mod.rs: stdout/file/ring-buffer logging and optional OpenTelemetry.
../../horsed/src/db/ and ../../horsed/migration/: SQLite schema and migrations.
../../horsed/src/options/: CLI surface.

Development Workflow

Identify whether the change belongs in horsed, cargo-work, or stable.
If the change alters protocol or server actions, inspect both ../../horsed/src/ssh/mod.rs and the client-side caller.
If the change alters persisted data, add or update a migration in ../../horsed/migration/.
Add or update tests before relying on manual validation.

Build and Test Commands

cargo build -p horsed
cargo test -p horsed --verbose
cargo test --workspace --verbose
just install-horsed
just install-horsed-with-trace

For migrations:

cargo run -p migration -- up
cargo run -p migration -- status
cargo run -p migration -- fresh

Testing Guidance

Existing server auth/setup coverage lives in ../../horsed/src/ssh/tests.rs.
Job registry behavior coverage lives in ../../horsed/src/ssh/jobs.rs (#[cfg(test)]).
When changing bootstrap auth or server action routing, extend those tests or add adjacent ones.
When changing logging or startup behavior, manual verification in a throwaway work directory is still useful because runtime side effects include DB, key, and log files.

Known Edges

horsed user mod and horsed user list are declared in the CLI but not implemented in main.rs.
The --dir CLI option is present but does not currently drive a directory change.
The service templates under ../../scripts/autostart/ may need foreground-mode adjustments if they are used with a process supervisor.

Change Patterns

Startup or lifecycle changes: start at ../../horsed/src/main.rs.
New remote action or protocol path: start at ../../horsed/src/ssh/mod.rs and the corresponding client command.
Job attach/list behavior: start at ../../horsed/src/ssh/jobs.rs and the job action in ../../horsed/src/ssh/mod.rs.
Setup enrollment logic: start at ../../horsed/src/ssh/setup.rs.
Health and observability changes: start at ../../horsed/src/ssh/health.rs and ../../horsed/src/logger/mod.rs.
Schema or user-key relation changes: start at ../../horsed/src/db/entity/ plus ../../horsed/migration/.

When Not To Use This Skill

Do not use this skill for normal remote builds or artifact retrieval; use the cargo-work skills instead.
Do not use this skill for day-2 deployment guidance; use workhorse-horsed-ops.

이 저장소의 다른 Skills

같은 저장소

workhorse-remote-access

uuhan/workhorse

Use when the user wants remote shell access or ad-hoc command execution through `cargo work`, including raw `cargo work -- ...` commands, stdin script execution with `cargo work exec`, `cargo work ssh`, port forwarding with `-L` or `-R`, environment injection, PTY allocation, shell selection, and reverse proxy setup with `-x` or `--all-proxy`.

2026-07-073

workhorse-cargo-work

uuhan/workhorse

Use as the entry skill for Workhorse `cargo work` tasks. It classifies the request first, then routes to the right sub-skill for remote Rust builds, remote shell or proxy access, or artifact retrieval, Git sync, and server inspection on a `horsed` server.

2026-07-053

workhorse

uuhan/workhorse

Use as the top-level entry skill for this repository. It classifies Workhorse requests first, then routes to the right dispatcher for `cargo work` client tasks or `horsed` server tasks, including remote builds, remote access, artifact sync, server setup, operations, and `horsed` development.

2026-07-053

workhorse-artifact-sync

uuhan/workhorse

Use when the user wants to fetch files or build outputs from a `horsed` server with `cargo work get` or `scp`, sync Git state with `cargo work push` or `pull`, inspect server status with `cargo work ping`, `health`, and `logs`, or inspect and attach running job output with `cargo work job`.

2026-07-053

workhorse-horsed-ops

uuhan/workhorse

Use when the user wants to operate a running `horsed` server, wire it into `systemd`, `launchd`, or Windows Task Scheduler, inspect logs and health, choose between foreground and daemon modes, or troubleshoot runtime problems around ports, file descriptors, working directory, and setup mode.

2026-07-053

workhorse-remote-build

uuhan/workhorse

Use when the user wants to run Rust build workflows on a `horsed` server via `cargo work`, including remote `build`, `test`, `check`, `clippy`, `run`, `install`, `doc`, `metadata`, `rustc`, `zigbuild`, and `just` commands, with target selection through `--repo`, `--repo-name`, or `--remote`.

2026-07-053

name	workhorse-horsed-dev
description	Use when the user wants to modify the `horsed` server implementation itself, including SSH server behavior, setup flow, logging, IPC, SQLite schema, migrations, service startup logic, or server-side tests.

Workhorse Horsed Dev

Overview

This skill is for changing horsed code, not just operating a deployed server. Use it when the task touches server-side actions, database schema, process lifecycle, logging, or setup behavior.

Code Map

../../horsed/src/main.rs: process model, CLI, daemon and foreground startup.
../../horsed/src/ssh/mod.rs: main SSH server on 2222 and action dispatch.
../../horsed/src/ssh/jobs.rs: in-memory job registry, bounded output buffers, and attach event stream.
../../horsed/src/ssh/setup.rs: first-user bootstrap server on 2223.
../../horsed/src/ssh/health.rs: health action and ulimit -n reporting.
../../horsed/src/logger/mod.rs: stdout/file/ring-buffer logging and optional OpenTelemetry.
../../horsed/src/db/ and ../../horsed/migration/: SQLite schema and migrations.
../../horsed/src/options/: CLI surface.

Development Workflow

Identify whether the change belongs in horsed, cargo-work, or stable.
If the change alters protocol or server actions, inspect both ../../horsed/src/ssh/mod.rs and the client-side caller.
If the change alters persisted data, add or update a migration in ../../horsed/migration/.
Add or update tests before relying on manual validation.

Build and Test Commands

cargo build -p horsed
cargo test -p horsed --verbose
cargo test --workspace --verbose
just install-horsed
just install-horsed-with-trace

For migrations:

cargo run -p migration -- up
cargo run -p migration -- status
cargo run -p migration -- fresh

Testing Guidance

Existing server auth/setup coverage lives in ../../horsed/src/ssh/tests.rs.
Job registry behavior coverage lives in ../../horsed/src/ssh/jobs.rs (#[cfg(test)]).
When changing bootstrap auth or server action routing, extend those tests or add adjacent ones.
When changing logging or startup behavior, manual verification in a throwaway work directory is still useful because runtime side effects include DB, key, and log files.

Known Edges

horsed user mod and horsed user list are declared in the CLI but not implemented in main.rs.
The --dir CLI option is present but does not currently drive a directory change.
The service templates under ../../scripts/autostart/ may need foreground-mode adjustments if they are used with a process supervisor.

Change Patterns

Startup or lifecycle changes: start at ../../horsed/src/main.rs.
New remote action or protocol path: start at ../../horsed/src/ssh/mod.rs and the corresponding client command.
Job attach/list behavior: start at ../../horsed/src/ssh/jobs.rs and the job action in ../../horsed/src/ssh/mod.rs.
Setup enrollment logic: start at ../../horsed/src/ssh/setup.rs.
Health and observability changes: start at ../../horsed/src/ssh/health.rs and ../../horsed/src/logger/mod.rs.
Schema or user-key relation changes: start at ../../horsed/src/db/entity/ plus ../../horsed/migration/.

When Not To Use This Skill

Do not use this skill for normal remote builds or artifact retrieval; use the cargo-work skills instead.
Do not use this skill for day-2 deployment guidance; use workhorse-horsed-ops.