使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/flyingnobita/flyingnobita-deliver --skill deliver-setup開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Set up delivery
Configure the requested repo for deliver (or flyingnobita-deliver). This is an idempotent setup operation, not a delivery run. Existing valid defaults need no repeated interview. Inside Deliver, join unresolved choices to its grilling stop.
- Read the repo's rules and the shared
configuration. Detect the host using host detection. Read only its adapter: Orca, Herdr, or Paseo.
- Run every check in prerequisites for the
selected host and report its table. For each failed required row, give the fix and its link, and apply it only on the user's approval. A blocking row (missing commit capability, helper or host component) stops setup before smoke tests. Then present the optional section separately.
- If legacy configuration or an old run exists, read
migration. Preview changes and inventory existing runs before proposing removal. Do not commandeer them.
- Resolve planner, implementer, reviewer and QA settings. Recommend a distinct
reviewer model/harness when available. Ask only for missing/unsupported choices and changes in authority. Keep the initiating orchestrator unchanged. Review concurrency, human schedule and landing separately from permissions. When changing a Herdr harness, choose compatible model, effort and mode together; see Changing a Herdr harness.
- Validate selected profiles through no-edit smoke tasks in a disposable
workspace under the confirmed host. Ask each to report only its identity and completion; compare requested/effective settings. Native settlement, release and cleanup must be verified. Do not mark a failed or unavailable launch validated or silently broaden its permissions. Use an isolated setup record; a smoke test grants no delivery brief/plan approval. Use purpose:"setup" and approved.setup with the concrete request/selected profiles as defined in run records. Orca and Herdr smoke jobs use role smoke with each selected profile in turn.
- Back up any existing project config. Write only approved project values,
preserving unknown keys and unrelated host tables. On Herdr, write role profiles only as [hosts.herdr.roles.<role>] tables, and migrate old top-level role tables as described in Herdr role table migration. Paseo profiles remain in Paseo; report required changes there rather than overwriting them. Keep legacy files and migration evidence while old runs may need them.
- Add a concise pointer to
docs/agents/delivery.tomlin the repo'sAGENTS.md
only when requested or approved. The autonomous merge rule still requires the separate explicit consent in Deliver's project rules. Optional tracker setup is not a prerequisite to this skill.
Done when every required prerequisite is ok or named as a blocker, every optional item was offered, settings are recorded, every selected profile has a verified result or explicit blocker, and every setup resource is removed or named as retained. Report the prerequisite table, changes, effective settings, permissions, smoke evidence and migration decisions. Commit through repository commit rules (or a configured custom commit skill); publication is separate.
Herdr role table migration
A Herdr project layer lives under [hosts.herdr.roles.<role>]. When docs/agents/delivery.toml has old top-level [planner], [implementer], [reviewer] or [qa] tables and no [hosts.herdr.roles.*], offer to move them:
- Back up the file and read the effective profiles first with `deliver-runtime
herdr-project-roles and profiles, passing [herdr-profiles.toml](../deliver/references/herdr-profiles.toml) as defaults`.
- Move each of the four role tables under
[hosts.herdr.roles.<role>], keeping
every key and value, including unknown keys.
- Leave
[delivery],[hosts], other host tables, comments and all unrelated
content in place.
- Show the proposed file or its diff and get approval before writing it.
- Repeat the profile reads and confirm the effective Herdr profiles are
unchanged and no layout warning is reported.
- Confirm no top-level role table remains; keep the backup as migration
evidence while old runs may need it.