deploy-qa

Automate development code deployment to QA environments via GitHub Actions.

224|136|Updated Jul 12, 2014
One-click install
npx skills add https://github.com/hmislk/hmis --skill deploy-qa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-qa
Source: https://github.com/hmislk/hmis/tree/main/.claude/skills/deploy-qa
Command: npx skills add https://github.com/hmislk/hmis --skill deploy-qa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deployments to QA environments often suffer from misconfigurations and inconsistent validations, causing delays in testing cycles.

Core Features & Use Cases

  • Pre-deployment checks for persistence.xml and environment configuration.
  • GitHub Actions-driven deployment to QA1 or QA2 with automatic builds and restarts.
  • End-to-end workflow suitable for CI/CD pipelines and staging readiness.

Quick Start

Trigger the QA deployment by merging development into the target qa1 or qa2 branch and monitor the GitHub Actions run.

Frequently Asked Questions about deploy-qa

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

FAQPage Schema
How do I automate deploying code to QA1 or QA2 environments using GitHub Actions?

Automate QA deployments by merging development code into the target qa1 or qa2 branch, which triggers a GitHub Actions workflow that builds the Maven project and restarts the application server.

What pre-deployment validations are needed for GitHub Actions CI/CD pipelines?

Pre-deployment validations for CI/CD pipelines include checking the persistence.xml file and handling repository branch configurations to prevent misconfigurations and testing delays.

How does the Maven build process work within a GitHub Actions QA deployment?

The Maven build process triggers automatically within the GitHub Actions workflow upon branch merge, compiling the development code and restarting the application server to complete the end-to-end pipeline.

Does the QA deployment workflow support staging readiness and CI/CD pipelines?

Yes, the GitHub Actions-driven workflow applies end-to-end pre-deployment checks and automated builds, making it suitable for CI/CD pipelines and staging readiness.

Why does my QA environment deployment fail after merging to the qa1 branch?

QA environment deployments often fail due to misconfigurations in persistence.xml or inconsistent environment validations, which the GitHub Actions pre-deployment checks are designed to catch.

Can I use deploy-qa for both QA1 and QA2 branch deployments?

Yes, deploy-qa handles deployments to both QA1 and QA2 environments by triggering Maven-based builds and application server restarts through GitHub Actions workflows.