Skip to content
Skills Library
DevOps & cloud · Automation

deploy-qa

/deploy-qa

Deploy to QA environment (QA1 or QA2). Use when deploying code to the QA testing environments via GitHub Actions. Includes pre-deployment checks for persistence.xml.

Repository
hmis ↗
Licence
GPL-3.0
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Deploy to QA environment (QA1 or QA2). Use when deploying code to the QA testing environments via GitHub Actions. Includes pre-deployment checks for persistence.xml.

Arguments

/deploy-qa [qa1|qa2]
Original author description

Deploy to QA environment (QA1 or QA2). Use when deploying code to the QA testing environments via GitHub Actions. Includes pre-deployment checks for persistence.xml.

How it works

  1. Arguments
  2. Pre-Deployment Checklist
  3. Deployment Process
  4. Post-Deployment
  5. Troubleshooting
Original SKILL.md headings · 56 lines, 182 words
SKILL.md preview
---
name: deploy-qa
description: >
  Deploy to QA environment (QA1 or QA2). Use when deploying code to the QA testing
  environments via GitHub Actions. Includes pre-deployment checks for persistence.xml.
disable-model-invocation: true
allowed-tools: Bash, Read, Grep
argument-hint: "[qa1|qa2]"
---

# Deploy to QA Environment

Deploy the latest development code to QA1 or QA2 via GitHub Actions.

## Arguments

- `$0` - Target environment: `qa1` or `qa2`

## Pre-Deployment Checklist

Before deploying, MUST verify:

1. **persistence.xml uses environment variables** (run `/verify-persistence` first)
2. **No hardcoded DDL generation paths**
3. **All changes committed and pushed**

## Deployment Process

### QA1 Deployment
```bash
# Merge development into qa1 branch
git fetch origin
git checkout qa1
git merge origin/development
git push origin qa1
```

### QA2 Deployment
```bash
# Merge development into qa2 branch
git fetch origin
git checkout qa2
git merge origin/development
git push origin qa2
```

GitHub Actions will automatically:
1. Build the application with Maven
2. Deploy to the target QA server
3. Restart the Payara application server

## Post-Deployment

- Monitor GitHub Actions for build status
- Check QA environment is accessible after deployment
- Verify the deployed feature works as expected

## Troubleshooting

If deployment fails:
1. Check GitHub Actions logs for build errors
2. Verify persistence.xml configuration
3. Check if QA server is accessible
4. See [QA Troubleshooting Guide](../../../developer_docs/deployment/qa-troubleshooting.md)

Versions

RepositoryScoreLicence
This page · hmislk/hmis100GPL-3.0
hmislk/hmis100GPL-3.0

Database snapshot: 13.11.2026 · package version 62f46e4d1d62 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100deployment
    Deploy applications to DigitalOcean App Platform via GitHub Actions with proper environment management and secrets handling. Use when setting up CI/CD pipelines, configuring staging/production environments, managing deployment secrets, or creating GitHub Actions workflows.
  • 100tl-deploy
    Monitor CI/CD deployment (GitHub Actions), run health checks, update YouGile. Deployment is triggered by git push (nacl-tl-ship), this skill monitors the result. Use when: deploy, check deploy status, verify deployment, or the user says "/nacl:tl-deploy".
  • 100vercel-deploy
    Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
  • 100vercel-deploy
    Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".
  • 100github-actions
    CI/CD workflow patterns, testing pipelines, deployment automation. Use when setting up GitHub Actions workflows for testing, building, linting, or deploying a fullstack app.
  • 100github-actions
    Build, test, and deploy applications using GitHub Actions workflows. Create CI/CD pipelines, configure runners, manage secrets, and automate software delivery. Use when working with GitHub repositories, automating builds, running tests, or deploying applications.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.