archflow-agent-devops-engineer

Configures CI/CD pipelines, deployment automation, and release management for the project's declared stack.

28|4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AZidan/archflow --skill archflow-agent-devops-engineer-azidan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archflow-agent-devops-engineer
Source: https://github.com/AZidan/archflow/tree/main/adapters/generic/.agents/skills/archflow-agent-devops-engineer
Command: npx skills add https://github.com/AZidan/archflow --skill archflow-agent-devops-engineer-azidan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up CI/CD pipelines, container packaging, and release processes is error-prone and often drifts from the project's actual stack. This Skill reads the project's declared stack configuration and builds pipelines, deployment configs, and release documentation that match it exactly, while enforcing a strict approval gate before anything reaches production. ## Core Features & Use Cases - Stack-Aware Pipeline Configuration: Reads stack from .archflow/project-settings.yaml and configures exactly the CI provider and hosting target named there, detecting existing pipeline config from the repo when fields are unset. - Release Management: Determines semantic versions from the change set, writes changelogs and release notes in the project's existing format, and prepares mobile store metadata per platform. - Production Safety Gate: Requires explicit user approval before every production deploy, store submission, DNS change, production migration, or credential rotation, and never merges to main. - Use Case: A team finishing a release phase asks the agent to ship version 1.2.0. The Skill verifies tests pass in CI, writes release notes to docs/releases/, tags the release, and stops to request approval before deploying to production. ## Quick Start Ask the agent to set up a CI/CD pipeline and prepare the next release based on the stack declared in .archflow/project-settings.yaml.

Frequently Asked Questions about archflow-agent-devops-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a CI/CD pipeline that matches my project's stack?

Declare your stack in .archflow/project-settings.yaml with ci, hosting, package_manager, and test fields, then invoke this role. It configures exactly the named CI provider and hosting target rather than substituting defaults, and detects existing pipeline config from the repo when fields are unset.

How does the release and versioning process work?

The agent determines the semantic version from the change set (breaking, feature, or fix), writes release notes grouped into features, fixes, and technical changes in the project's changelog format, and records rollback strategy. Output goes to docs/releases/ and the CI provider's workflow directory.

Can this deploy to production automatically without approval?

No. Every production deploy, store submission, DNS change, production migration, or credential rotation requires explicit per-deploy user approval. Approval for one deploy never covers the next, and the agent stops and reports if approval is unavailable.

What happens if the stack configuration is missing or incomplete?

The agent detects pipeline evidence from the repo first: existing CI config, container files, manifests, and available CLI binaries. It then reports what it found and asks the user to confirm before writing any config, never inventing a provider on its own.

Does it support mobile app deployment to app stores?

Yes, when stack.mobile is set. It increments build numbers per release, pulls signing material from the secret store, produces optimized release builds with symbol files, and uploads through the platform's distribution tooling to a test track first. Store submission still requires explicit approval.