testing-and-ci — Terraform 테스팅 testing-and-ci, neptune, community, Terraform 테스팅, ide skills, OpenTofu 자동화, Github Actions CI, Go 테스트 워크플ロー, golangci-lint 통합, Makefile 경로 필터링

v1.0.0

이 스킬 정보

인프라스트럭처를 코드로 관리하는 에이전트에게 적합하며 Terraform 및 OpenTofu 워크플로우 테스트를 자동화하기 위해 Github Actions를 사용한다 테스팅과 CI는 Terraform와 OpenTofu를 사용하여 자동화 테스트와 지속적 통합을 구현하는 과정입니다

기능

Terraform와 OpenTofu 통합
Github Actions의 Pull Request 자동화
Go 테스트와 포맷팅
golangci-lint 통합
Makefile과 Go 파일의 경로 필터링

# Core Topics

devopsfactory-io devopsfactory-io
[3]
[0]
Updated: 3/16/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
29
Canonical Locale
en
Detected Body Locale
en

인프라스트럭처를 코드로 관리하는 에이전트에게 적합하며 Terraform 및 OpenTofu 워크플로우 테스트를 자동화하기 위해 Github Actions를 사용한다 테스팅과 CI는 Terraform와 OpenTofu를 사용하여 자동화 테스트와 지속적 통합을 구현하는 과정입니다

이 스킬을 사용하는 이유

에이전트에게 Go 프로젝트의 자동 테스트, 형식화, 빌드를 가능하게 하며 Github Actions를 사용하고 make test-all 및 make check-fmt와 같은 명령어를 활용하며 golangci-lint와 통합하여 포괄적인 코드 검증을 수행한다

최적의 용도

인프라스트럭처를 코드로 관리하는 에이전트에게 적합하며 Terraform 및 OpenTofu 워크플로우 테스트를 자동화하기 위해 Github Actions를 사용한다

실행 가능한 사용 사례 for testing-and-ci

make test-all을 사용하여 Go 테스트套件을 자동화한다
make check-fmt를 사용하여 일관된 코드 형식화를 강제한다
golangci-lint를 통합하여 고급 코드 linting 및 검증을 수행한다

! 보안 및 제한 사항

  • Github Actions 설정이 필요하다
  • Go 프로젝트에만 제한된다
  • linting 기능을 구현하기 위해 golangci-lint 설치에 의존한다

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is testing-and-ci?

인프라스트럭처를 코드로 관리하는 에이전트에게 적합하며 Terraform 및 OpenTofu 워크플로우 테스트를 자동화하기 위해 Github Actions를 사용한다 테스팅과 CI는 Terraform와 OpenTofu를 사용하여 자동화 테스트와 지속적 통합을 구현하는 과정입니다

How do I install testing-and-ci?

Run the command: npx killer-skills add devopsfactory-io/neptune/testing-and-ci. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for testing-and-ci?

Key use cases include: make test-all을 사용하여 Go 테스트套件을 자동화한다, make check-fmt를 사용하여 일관된 코드 형식화를 강제한다, golangci-lint를 통합하여 고급 코드 linting 및 검증을 수행한다.

Which IDEs are compatible with testing-and-ci?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for testing-and-ci?

Github Actions 설정이 필요하다. Go 프로젝트에만 제한된다. linting 기능을 구현하기 위해 golangci-lint 설치에 의존한다.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add devopsfactory-io/neptune/testing-and-ci. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use testing-and-ci immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

testing-and-ci

Install testing-and-ci, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Testing and CI

Commands

  • make test-all – Run all Go tests (go test ./...).
  • make check-fmt – Verify Go formatting (gofmt -s -l); fails if any file needs formatting.
  • make lint – Run golangci-lint (requires golangci-lint installed).
  • make build – Build the neptune binary.

CI Workflows

  • test.yml – On push to main/release-* and on PRs. Path filter for Go files and Makefile. Runs make test-all and make check-fmt.
  • lint.yml – On PRs. Path filter for Go and lint config. Runs golangci-lint.
  • labeler.yml – On pull_request. Runs actions/labeler with .github/labeler.yml (path and head-branch rules).
  • label-old-prs.yml – workflow_dispatch. Backfills labels: applies same rules as labeler to head branch and PR title (labeler has no branch context on manual run), then runs the labeler for path-based labels. Use state and limit inputs.
  • release.yml – On push of tags v*.*.*. Runs GoReleaser to create the GitHub Release and artifacts.

Adding Tests

  • Place *_test.go in the same package as the code (e.g. internal/config/loader_test.go).
  • Use table-driven tests for multiple cases; single-case tests are fine when appropriate.
  • Existing test packages: internal/config, internal/git, internal/run, internal/notifications/github. Add or extend tests when touching those areas or adding new packages.
  • Do not depend on live GitHub or GCS in unit tests; use mocks or stubs.

관련 스킬

Looking for an alternative to testing-and-ci or another community skill for your workflow? Explore these related open-source skills.

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
인공지능

widget-generator

Logo of f
f

prompts.chat 피드 시스템을 위한 사용자 지정 가능한 위젯 플러그인을 생성합니다

149.6k
0
인공지능

flags

Logo of vercel
vercel

리액트 프레임워크

138.4k
0
브라우저

pr-review

Logo of pytorch
pytorch

파이썬에서 텐서와 동적 신경망 구현 및 강력한 GPU 가속 지원

98.6k
0
개발자