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

service-deploy

스타29

포크7

업데이트2026년 6월 5일 21:26

Plan, package, verify, deploy, inspect, and roll back services using Harnessy CI/deploy profiles with Hostinger as the first provider adapter.

설치

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

Manus에서 실행

출처

Flow-Research

Flow-Research/harnessy

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

다운로드

Manus에서 실행

Service Deploy

Purpose

Provide a Harnessy-standard deployment capability that is CI/profile/evidence driven. The skill normalizes deployment planning, packaging, provider policy, Hostinger adapter selection, smoke evidence, and rollback records behind the harness-deploy command.

Inputs

.jarvis/context/profiles/ci.json
.jarvis/context/profiles/deploy.json
optional .jarvis/context/profiles/qa.json
command intent: plan, check, configure, targets, ssh-setup, package, deploy, status, logs, or rollback
Template paths are resolved from ${AGENTS_SKILLS_ROOT}/service-deploy/.

Steps

Read ${AGENTS_SKILLS_ROOT}/service-deploy/commands/service-deploy.md.
Run ${AGENTS_SKILLS_ROOT}/service-deploy/scripts/harness-deploy <command> for deterministic behavior.
For deployment work, prefer CI tag-driven execution. Use --local-override only when the user explicitly asks for local deploy.
Do not call raw Hostinger tools directly unless the Harnessy wrapper instructs you to do so.
Treat billing, purchase, destructive deletion, destructive backup restore, and DNS mutation as out of scope for v1.
Treat Docker Compose, systemd, static, managed Node, and generic process deployment as runtime modes selected by .jarvis/context/profiles/deploy.json.
Use harness-deploy configure for gitignored local provider credential setup, harness-deploy targets for read-only Hostinger VPS discovery, and harness-deploy ssh-setup for SSH key attachment/verification.
Preserve evidence under .jarvis/context/deployments/<run-id>/ when persistence is enabled.

Deterministic Logic

scripts/harness-deploy
- Input: CI/deploy profile files plus command flags.
- Output: human summary or JSON with profile paths, gate results, package hash, provider target, and evidence path.
- Side effects: package, deploy, and rollback may write deployment evidence under .jarvis/context/deployments/.

Output

Deployment plan, gate report, package metadata, deployment evidence, provider status/log summary, or rollback evidence.

이 저장소의 다른 Skills

같은 저장소

code-refactorer

Flow-Research/harnessy

Autonomous code refactoring agent that rewrites messy functions, splits large files, removes duplication, improves naming, enforces structure, and preserves behavior.

2026-06-0629

anytype-skill

Flow-Research/harnessy

Interact with Anytype's local REST API to manage spaces, objects, types, properties, tags, lists, and search.

2026-06-0529

api-integration-codegen

Flow-Research/harnessy

Generate API integration test suites from Harnessy regression artifacts using a QA profile plus optional delivery-profile adapters.

2026-06-0529

browser-integration-codegen

Flow-Research/harnessy

Generate browser integration suites from Harnessy regression artifacts using a QA profile plus optional delivery-profile adapters for fixtures, routes, and helper imports.

2026-06-0529

build-e2e

Flow-Research/harnessy

End-to-end product development orchestrator with human-in-the-loop reviews.

2026-06-0529

context-sync

Flow-Research/harnessy

Safe repo pull/push workflow that targets the repository integration branch, uses deterministic planning, and keeps PRs moving with a bounded autonomous resolution loop.

2026-06-0529

Service Deploy

Purpose

Inputs

.jarvis/context/profiles/ci.json

.jarvis/context/profiles/deploy.json

optional .jarvis/context/profiles/qa.json

command intent: plan, check, configure, targets, ssh-setup, package, deploy, status, logs, or rollback

Template paths are resolved from ${AGENTS_SKILLS_ROOT}/service-deploy/.

Steps

Read ${AGENTS_SKILLS_ROOT}/service-deploy/commands/service-deploy.md.

Run ${AGENTS_SKILLS_ROOT}/service-deploy/scripts/harness-deploy <command> for deterministic behavior.

For deployment work, prefer CI tag-driven execution. Use --local-override only when the user explicitly asks for local deploy.

Do not call raw Hostinger tools directly unless the Harnessy wrapper instructs you to do so.

Treat billing, purchase, destructive deletion, destructive backup restore, and DNS mutation as out of scope for v1.

Treat Docker Compose, systemd, static, managed Node, and generic process deployment as runtime modes selected by .jarvis/context/profiles/deploy.json.

Use harness-deploy configure for gitignored local provider credential setup, harness-deploy targets for read-only Hostinger VPS discovery, and harness-deploy ssh-setup for SSH key attachment/verification.

Preserve evidence under .jarvis/context/deployments/<run-id>/ when persistence is enabled.

Deterministic Logic

scripts/harness-deploy

Input: CI/deploy profile files plus command flags.
Output: human summary or JSON with profile paths, gate results, package hash, provider target, and evidence path.
Side effects: package, deploy, and rollback may write deployment evidence under .jarvis/context/deployments/.

Output

Deployment plan, gate report, package metadata, deployment evidence, provider status/log summary, or rollback evidence.

name	service-deploy
description	Plan, package, verify, deploy, inspect, and roll back services using Harnessy CI/deploy profiles with Hostinger as the first provider adapter.
disable-model-invocation	false
allowed-tools	Read, Grep, Glob, Bash
argument-hint	plan\|check\|configure\|targets\|ssh-setup\|package\|deploy\|status\|logs\|rollback [--env <name>] [--json] [--dry-run] [--local-override]

name	service-deploy
description	Plan, package, verify, deploy, inspect, and roll back services using Harnessy CI/deploy profiles with Hostinger as the first provider adapter.
disable-model-invocation	false
allowed-tools	Read, Grep, Glob, Bash
argument-hint	plan\|check\|configure\|targets\|ssh-setup\|package\|deploy\|status\|logs\|rollback [--env <name>] [--json] [--dry-run] [--local-override]