ワンクリックでManusで任意のスキルを実行

deploy-anywhere

スター3

フォーク0

更新日2026年7月5日 07:23

Deploy with unified build/test/deploy intent across providers using .agent-loom/deploy.yml and per-provider adapters. Load when the user asks to deploy, ship to preview, release to production, or run a provider-agnostic deploy flow. Also triggers on "deploy anywhere", "deploy to Vercel", "deploy with GitHub Actions", "preview deploy", or "ship this". Runs preflight before any deploy — stops on missing secrets. Pairs with ci-cd-and-automation for pipeline design. Ships vercel and github-actions adapters; extensible adapter interface.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

dvy1987

dvy1987/agent-loom

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Deploy Anywhere

One deploy intent — read or scaffold .agent-loom/deploy.yml, detect provider, preflight secrets, run adapter steps, return URL + rollback command.

Hard Rules

Run scripts/preflight.py before any deploy — no partial deploys on missing config/secrets. Secrets by name only in files — never write credential values to repo. Shipped adapters: vercel, github-actions — see references/adapters/. Run test_cmd from config when present before build. Emit deployment summary: target, URL/status, rollback command.

Workflow

Step 1 — Read or scaffold config

Load .agent-loom/deploy.yml per DEPLOY-SCHEMA.md. If missing, scaffold from repo signals (vercel.json, .github/workflows/) and confirm with user.

Step 2 — Detect target

Config targets[] first; else repo signals; else ask.

Step 3 — Preflight

python3 .agents/skills/deploy-anywhere/scripts/preflight.py

On fail: list missing items exactly; stop.

Step 4 — Test + build

Run test_cmd then build_cmd from config.

Step 5 — Run adapter

Load references/adapters/<provider>.md. Execute documented CLI sequence.

Step 6 — Summarize

## Deploy summary
Target: [provider] ([preview|prod])
URL: [url or run link]
Rollback: [command]

Gotchas

Vercel prebuilt flow requires vercel build before vercel deploy --prebuilt.
Local gh workflow run needs gh auth — not the same as CI token.
Multiple targets deploy sequentially — confirm order with user.

Output Format

See Step 6 summary template.

Examples

Teaser: deploy.yml with vercel target → preflight OK → build → deploy URL returned.

Full pairs: references/examples.md

Common Rationalizations

Excuse	Reality
"Skip preflight — I'll add secrets later"	Half-configured deploys fail opaquely.
"Embed token in deploy.yml for now"	Secrets in repo leak — names only.
"Skip tests this once"	test_cmd exists for a reason.
"One adapter fits all"	Use the adapter file — don't improvise CLI.
"Rollback is optional"	Always emit rollback command.

Verification

preflight.py passed
test_cmd run when configured
Adapter steps from reference file
Rollback command in summary

Red Flags

Deploy attempted after preflight fail
Secret value written to yaml
Unknown provider without adapter file

Prune Log

Last pruned: 2026-07-05

Initial release from high-leverage skill spec (Skill 3 family)

Impact Report

Deploy: [provider] | Preflight: [pass/fail] | URL: [url or n/a]

このリポジトリの他の Skills

同じリポジトリ

code-review-crsp

dvy1987/agent-loom

Review code changes for correctness, completeness, bugs, edge cases, and quality. Load when the user explicitly asks to review code, check a PR, review a diff, audit recent changes, or verify an implementation matches requirements. Also triggers on "review this code", "check this PR", "review my changes", "code review", "did this implement correctly", "audit this diff", or any explicit request for a formal code review. Do NOT load for "review changes for context" or "review what happened" — those are requests to read code, not to perform a formal review.

2026-07-093

debug-and-fix

dvy1987/agent-loom

Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.

2026-07-093

git-workflow-and-versioning

dvy1987/agent-loom

Structure git work with atomic commits, conventional messages, short-lived branches, and pre-commit hygiene. Load when committing, branching, resolving merge conflicts, organizing parallel work, or reviewing git history. Also triggers on "git workflow", "commit message", "conventional commits", "atomic commit", "branch strategy", "git worktree", "how should I commit this". Does not replace project-specific hook policies — complements them.

2026-07-093

implementation-plan

dvy1987/agent-loom

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

2026-07-093

incremental-implementation

dvy1987/agent-loom

Deliver multi-file changes in thin vertical slices — implement, test, verify, commit, repeat. Load when implementing a feature from a plan, building across more than one file, refactoring, or when tempted to land a large change in one pass. Also triggers on "incremental implementation", "vertical slice", "thin slice", "one slice at a time", "don't do it all at once". Routes single-file fixes to direct execution. Pairs with test-driven-development and git-workflow-and-versioning.

2026-07-093

test-driven-development

dvy1987/agent-loom

Apply the Red-Green-Refactor cycle to software development. Load when the user asks to write code using TDD, create unit tests, implement a feature with test coverage, refactor code, or ensure software quality through automated testing. Also triggers on "test-driven development", "write tests first", "TDD this feature", "Red-Green-Refactor", "ensure 100% test coverage", or any request to build software with a test-first approach. Supports unit, integration, and end-to-end testing strategies.

2026-07-093

name	deploy-anywhere
description	Deploy with unified build/test/deploy intent across providers using .agent-loom/deploy.yml and per-provider adapters. Load when the user asks to deploy, ship to preview, release to production, or run a provider-agnostic deploy flow. Also triggers on "deploy anywhere", "deploy to Vercel", "deploy with GitHub Actions", "preview deploy", or "ship this". Runs preflight before any deploy — stops on missing secrets. Pairs with ci-cd-and-automation for pipeline design. Ships vercel and github-actions adapters; extensible adapter interface.
license	MIT
metadata	{"author":"dvy1987","version":"1.0","category":"project-specific","sources":"nikolareljin/ci-orchestrator, universal-deploy/universal-deploy, vercel/examples","resources":{"references":["DEPLOY-SCHEMA.md","adapters/vercel.md","adapters/github-actions.md","examples.md"],"scripts":["preflight.py"]}}

Deploy Anywhere

One deploy intent — read or scaffold .agent-loom/deploy.yml, detect provider, preflight secrets, run adapter steps, return URL + rollback command.

Hard Rules

Workflow

Step 1 — Read or scaffold config

Load .agent-loom/deploy.yml per DEPLOY-SCHEMA.md. If missing, scaffold from repo signals (vercel.json, .github/workflows/) and confirm with user.

Step 2 — Detect target

Config targets[] first; else repo signals; else ask.

Step 3 — Preflight

python3 .agents/skills/deploy-anywhere/scripts/preflight.py

On fail: list missing items exactly; stop.

Step 4 — Test + build

Run test_cmd then build_cmd from config.

Step 5 — Run adapter

Load references/adapters/<provider>.md. Execute documented CLI sequence.

Step 6 — Summarize

## Deploy summary
Target: [provider] ([preview|prod])
URL: [url or run link]
Rollback: [command]

Gotchas

Vercel prebuilt flow requires vercel build before vercel deploy --prebuilt.
Local gh workflow run needs gh auth — not the same as CI token.
Multiple targets deploy sequentially — confirm order with user.

Output Format

See Step 6 summary template.

Examples

Teaser: deploy.yml with vercel target → preflight OK → build → deploy URL returned.

Full pairs: references/examples.md

Common Rationalizations

Excuse	Reality
"Skip preflight — I'll add secrets later"	Half-configured deploys fail opaquely.
"Embed token in deploy.yml for now"	Secrets in repo leak — names only.
"Skip tests this once"	test_cmd exists for a reason.
"One adapter fits all"	Use the adapter file — don't improvise CLI.
"Rollback is optional"	Always emit rollback command.

Verification

preflight.py passed
test_cmd run when configured
Adapter steps from reference file
Rollback command in summary

Red Flags

Deploy attempted after preflight fail
Secret value written to yaml
Unknown provider without adapter file

Prune Log

Last pruned: 2026-07-05

Initial release from high-leverage skill spec (Skill 3 family)

Impact Report

Deploy: [provider] | Preflight: [pass/fail] | URL: [url or n/a]