deploy-config

Étoiles10

Forks3

Mis à jour18 avril 2026 à 19:36

Meta-skill: deploys the full agentic configuration to a target project — AGENTS.md composition, vendor file generation, and skill deployment — in a single workflow. Invoked when the user asks to deploy or update agent config, sync the agentic setup, or set up agents in a project.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

soulcodex

soulcodex/agentic

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	deploy-config
description	Meta-skill: deploys the full agentic configuration to a target project — AGENTS.md composition, vendor file generation, and skill deployment — in a single workflow. Invoked when the user asks to deploy or update agent config, sync the agentic setup, or set up agents in a project.
version	1.0.0
tags	["agentic","meta","deployment"]
resources	[]
vendor_support	{"claude":"native","opencode":"native","copilot":"prompt-inject","codex":"prompt-inject","gemini":"prompt-inject"}

Deploy Config Skill

Deploy the complete agentic configuration to a target project.

Step 1 — Confirm Target and Profile

Ask the user:

Target project path (absolute or relative)
Profile name (run just list-profiles if unsure)
Skills to deploy (run just list-skills if unsure; can be "all" or a comma-separated list)
Which vendors to generate files for

Step 2 — Check for Existing Config

Read {target}/.agentic/config.yaml if it exists. If it does, show the current profile and version, and ask if the user wants to update or replace.

Step 3 — Run the Full Deploy Pipeline

# 1. Compose AGENTS.md from the profile
just compose {profile} {target}

# 2. Generate vendor-specific files
just vendor-gen {target} --vendors {vendors}

# 3. Deploy selected skills
just deploy-skills {target} --skills {skills}

Step 4 — Verify Output

After deploying, list the files created in the target project:

AGENTS.md — primary agent instructions
CLAUDE.md — Claude adapter (if claude vendor enabled)
.github/copilot-instructions.md — Copilot adapter (if copilot enabled)
GEMINI.md — Gemini primary context file (auto-discovered, if gemini enabled)
.gemini/system.md — Gemini system-prompt override (requires GEMINI_SYSTEM_MD=1, if gemini enabled)
.gemini/skills/ — Gemini skills directory (symlinked, if gemini enabled)
.claude/skills/*/ — deployed skill directories (if claude enabled)
.agentic/config.yaml — lock file recording what was deployed

Step 5 — Next Steps

Suggest to the user:

Commit the generated files to the target project
Run just validate {target} to verify the config is valid
Run just sync-check {target} periodically to detect drift from the library

Plus depuis ce dépôt

même dépôt

terraform-infrastructure

soulcodex/agentic

Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk classification, version guards, and rollback contract to `terraform-risk-playbook`. Invoked when the user asks to write Terraform, set up infrastructure as code, or review IaC.

2026-06-2710

create-terraform-module

soulcodex/agentic

Creates or updates AWS-oriented Terraform module structure and implementation scaffolding. Focuses on file layout, variable/output contracts, provider and version constraints, tagging standards, safe composition patterns, and address-stability guardrails.

2026-06-2710

create-terraform-tests

soulcodex/agentic

Designs and implements Terraform module tests for AWS-targeted modules. Covers terraform-native tests, validation gates, fixture composition, and risk-focused assertions for regressions, address migration, and unsafe changes.

2026-06-2710

design-aws-terraform-iac

soulcodex/agentic

Designs AWS-targeted Terraform infrastructure plans before implementation. Focuses on service selection, module boundaries, state/backends, environment separation, security/compliance guardrails, acceptance criteria, and explicit risk/validation assumptions.

2026-06-2710

terraform-risk-playbook

soulcodex/agentic

Diagnoses Terraform/OpenTofu risk before generating changes. Defines the response contract, failure-mode routing, version/runtime guards, validation commands, and rollback expectations for modules, tests, CI, and state work.

2026-06-2710

use-aws-mini-stack-emulator

soulcodex/agentic

Uses lightweight AWS stack emulation for faster local Terraform iteration. Defines what can be safely validated locally, compatibility caveats, and the handoff boundary to real-AWS verification and reviewed plan/apply flows.

2026-06-2710

name	deploy-config
description	Meta-skill: deploys the full agentic configuration to a target project — AGENTS.md composition, vendor file generation, and skill deployment — in a single workflow. Invoked when the user asks to deploy or update agent config, sync the agentic setup, or set up agents in a project.
version	1.0.0
tags	["agentic","meta","deployment"]
resources	[]
vendor_support	{"claude":"native","opencode":"native","copilot":"prompt-inject","codex":"prompt-inject","gemini":"prompt-inject"}

Deploy Config Skill

Deploy the complete agentic configuration to a target project.

Step 1 — Confirm Target and Profile

Ask the user:

Target project path (absolute or relative)
Profile name (run just list-profiles if unsure)
Skills to deploy (run just list-skills if unsure; can be "all" or a comma-separated list)
Which vendors to generate files for

Step 2 — Check for Existing Config

Read {target}/.agentic/config.yaml if it exists. If it does, show the current profile and version, and ask if the user wants to update or replace.

Step 3 — Run the Full Deploy Pipeline

# 1. Compose AGENTS.md from the profile
just compose {profile} {target}

# 2. Generate vendor-specific files
just vendor-gen {target} --vendors {vendors}

# 3. Deploy selected skills
just deploy-skills {target} --skills {skills}

Step 4 — Verify Output

After deploying, list the files created in the target project:

AGENTS.md — primary agent instructions
CLAUDE.md — Claude adapter (if claude vendor enabled)
.github/copilot-instructions.md — Copilot adapter (if copilot enabled)
GEMINI.md — Gemini primary context file (auto-discovered, if gemini enabled)
.gemini/system.md — Gemini system-prompt override (requires GEMINI_SYSTEM_MD=1, if gemini enabled)
.gemini/skills/ — Gemini skills directory (symlinked, if gemini enabled)
.claude/skills/*/ — deployed skill directories (if claude enabled)
.agentic/config.yaml — lock file recording what was deployed

Step 5 — Next Steps

Suggest to the user:

Commit the generated files to the target project
Run just validate {target} to verify the config is valid
Run just sync-check {target} periodically to detect drift from the library