원클릭으로 Manus에서 모든 스킬 실행

ci-cd-release

스타0

포크0

업데이트2026년 5월 21일 07:00

Manage CI/CD pipelines, GitHub Actions, build scripts, changelog, and release workflows. Trigger on /ci-cd-release, or when editing workflows, releasing, fixing CI failures, or creating changelogs.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

JonusNattapong

JonusNattapong/Dek1Skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

CI/CD Release

Handle CI/CD, build pipelines, and releases safely. CI/CD is high-risk — mistakes block the whole team.

Workflow

1. Understand the pipeline

Read the workflow file (.github/workflows/, .gitlab-ci.yml, etc.).
Identify triggers (push, PR, tag, schedule, manual).
Understand the stages (lint, test, build, deploy).
Note which secrets/env vars are required.

2. CI failure diagnosis

Reproduce locally if possible (same Node/Bun version, same OS).
Check if the failure is pre-existing (failing before your change).
Look at CI logs — find the exact command and error, not just the red status.
Distinguish: infra failure (runner, cache, timeout) vs code failure.

3. Release workflow

Confirm the release checklist (tests pass, changelog updated, version bumped).
Use the project's release script or convention — do not invent a new process.
If tagging, verify the tag matches the version in package.json.
If publishing, confirm package contents (files field, dist existence).

4. Changelog

Read existing changelog format and follow it.
Categorize changes: Added, Changed, Fixed, Removed, Security.
Do not overwrite unreleased changes.

Rules

Do not edit CI workflows that require secrets you cannot verify.
Do not trigger releases without explicit confirmation.
Document CI env vars (without exposing values).
Test workflow changes on a branch first, not main.

Experience Log

This skill learns from experience. Mechanism:

Read .claude/experience/'"$s"'.md at skill start to benefit from past lessons.
Write to .claude/experience/'"$s"'.md after use if you learned something new.
Format: YYYY-MM-DD: <lesson> — one line per entry.
Evolve: If the same issue repeats 3+ times, update this SKILL.md itself.

이 저장소의 다른 Skills

같은 저장소

agent-tool-safety

JonusNattapong/Dek1Skills

Control shell, filesystem, MCP, browser, external APIs, and risky tools. Enforce read-only-before-write, least-privilege, and verification discipline. Trigger on /agent-tool-safety, or when using shell commands, file operations, MCP tools, browser automation, or external APIs.

2026-05-210

ai-coding-agent-review

JonusNattapong/Dek1Skills

Final sanity check on AI-generated code before merging. Run the checklist to catch common failure modes. Trigger on /ai-coding-agent-review, or before finalizing any significant AI-generated change.

2026-05-210

api-design

JonusNattapong/Dek1Skills

Review API design — endpoints, types, contracts, error handling, versioning, and consistency. Trigger on /api-design, or when designing or reviewing API specifications.

2026-05-210

api-implementation

JonusNattapong/Dek1Skills

Implement backend API endpoints — routing, middleware, input validation, error handling, authentication, rate limiting, file upload. Trigger on /api-implementation, or when building endpoints, adding middleware, handling file uploads, or implementing API security.

2026-05-210

architecture-decision

JonusNattapong/Dek1Skills

Record architecture decisions as ADRs — compare options, document trade-offs, and track rationale. Trigger on /architecture-decision, or when choosing libraries, designing modules, splitting systems, or making significant technical decisions.

2026-05-210

ask-less-execution

JonusNattapong/Dek1Skills

Make the agent continue work without asking unnecessary questions. Enforce the ask-less policy from CLAUDE.md. Trigger on /ask-less-execution, or when the agent is asking too many clarifying questions instead of discovering answers.

2026-05-210

name	ci-cd-release
description	Manage CI/CD pipelines, GitHub Actions, build scripts, changelog, and release workflows. Trigger on /ci-cd-release, or when editing workflows, releasing, fixing CI failures, or creating changelogs.
user-invocable	true
allowed-tools	Read, Grep, Glob, Bash, Edit

CI/CD Release

Handle CI/CD, build pipelines, and releases safely. CI/CD is high-risk — mistakes block the whole team.

Workflow

1. Understand the pipeline

Read the workflow file (.github/workflows/, .gitlab-ci.yml, etc.).
Identify triggers (push, PR, tag, schedule, manual).
Understand the stages (lint, test, build, deploy).
Note which secrets/env vars are required.

2. CI failure diagnosis

Reproduce locally if possible (same Node/Bun version, same OS).
Check if the failure is pre-existing (failing before your change).
Look at CI logs — find the exact command and error, not just the red status.
Distinguish: infra failure (runner, cache, timeout) vs code failure.

3. Release workflow

Confirm the release checklist (tests pass, changelog updated, version bumped).
Use the project's release script or convention — do not invent a new process.
If tagging, verify the tag matches the version in package.json.
If publishing, confirm package contents (files field, dist existence).

4. Changelog

Read existing changelog format and follow it.
Categorize changes: Added, Changed, Fixed, Removed, Security.
Do not overwrite unreleased changes.

Rules

Do not edit CI workflows that require secrets you cannot verify.
Do not trigger releases without explicit confirmation.
Document CI env vars (without exposing values).
Test workflow changes on a branch first, not main.

Experience Log

This skill learns from experience. Mechanism:

Read .claude/experience/'"$s"'.md at skill start to benefit from past lessons.
Write to .claude/experience/'"$s"'.md after use if you learned something new.
Format: YYYY-MM-DD: <lesson> — one line per entry.
Evolve: If the same issue repeats 3+ times, update this SKILL.md itself.