deployer

Automate external project deployments and retrieve status via GitHub API calls.

Updated Dec 11, 2025
One-click install
npx skills add https://github.com/semicolon-devteam/semo --skill deployer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deployer
Source: https://github.com/semicolon-devteam/semo/tree/main/semo-skills/deployer
Command: npx skills add https://github.com/semicolon-devteam/semo --skill deployer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates external project deployment management and status 조회 based on project alias and environment, reducing manual coordination and human errors.

Core Features & Use Cases

  • Alias-based deployment: Deploy external projects using project alias and environment (e.g., "랜드 stg 배포").
  • Milestone management: Close or query milestones to trigger releases.
  • Status reporting: Retrieve deployment status with clear, actionable output and links to CI/CD dashboards.

Quick Start

예: "랜드 stg 배포"를 실행하고, Milestone close를 수행해 배포를 트리거합니다.

Frequently Asked Questions about deployer

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

FAQPage Schema
How do I automate deployment of external projects to different environments?

Deployment automation uses project aliases and environment names (DEV, STG, PRD) to trigger deployments without manual coordination. This Skill maps aliases from memory, invokes GitHub API calls, and manages milestones to automate the full deployment workflow across environments.

Can I deploy using project aliases and track deployment status?

Yes. This Skill retrieves deployment status by querying project alias and environment, returning structured output with actionable links to CI/CD dashboards. Status inquiries like 'What is deployed to STG?' or 'What is the latest PRD release?' are handled automatically.

How does milestone-based deployment triggering work with GitHub?

Milestone-based deployment closes milestones via GitHub API to trigger releases and deployments. The Skill manages milestone operations, retrieves labels and branches, and produces structured outputs that integrate with GitHub-Actions CI/CD pipelines.

What GitHub API integrations are required for deployment automation?

Deployment automation requires GitHub API access to query milestones, labels, releases, and branches. This Skill handles API invocation and data retrieval, mapping project metadata to environment-specific deployment actions without manual GitHub interactions.

When should I use alias-based deployment instead of direct environment names?

Project aliases simplify deployment by storing project-to-repository mappings in memory, reducing manual typing and errors. Use aliases when managing multiple external projects across environments to streamline deployment requests and status checks.