How do I install the CI Script Only Run skill?

Run npx skillmds@latest add chewiebug/ci-script-only-run in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI Script Only Run safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI Script Only Run?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI Script Only Run free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CI Script Only Run?

chewiebug (@chewiebug) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI Script Only Run by chewiebug — Agent Skill

Name: CI Script Only Run
Author: chewiebug

File contents

What I do

Simulate GCViewer CI behavior locally without deploying.
Reproduce one of three CI paths:
- pull request verification
- develop snapshot (dry-run deploy path)
- master release (dry-run release/push path)
Allow selecting Java runtime from:
- E:/swdevelopment/java/openjdk-8
- E:/swdevelopment/java/openjdk-17
- E:/swdevelopment/java/openjdk-21
- E:/swdevelopment/java/openjdk-25

When to use me

Use this when you want a local CI-equivalent dry run of cicd/gcviewer-script.sh and a concise proof summary of the path taken and dry-run behavior.

Workflow

1) Confirm repository and prerequisites

Verify current workspace is GCViewer repo root:
- git rev-parse --show-toplevel
- ensure cicd/gcviewer-script.sh exists
Verify required tools:
- bash --version
- mvn -v
If any prerequisite fails, stop and report the issue.

2) Ask which CI dry run to simulate

Ask:

pull request
develop snapshot
master release
cancel

If user selects cancel, stop.

3) Ask which JDK to use

Ask:

openjdk-8
openjdk-17
openjdk-21
openjdk-25
cancel

If user selects cancel, stop.

Set:

JAVA_HOME = E:/swdevelopment/java/<selected-jdk>
DRY_RUN=true for all runs.

4) Execute selected dry run via Git Bash

Run the appropriate command from the repo root. Replace <selected-jdk> with openjdk-8, openjdk-17, openjdk-21, or openjdk-25.

Option A: pull request

JAVA_HOME=E:/swdevelopment/java/<selected-jdk> \
DRY_RUN=true \
GITHUB_EVENT_NAME=pull_request \
GITHUB_HEAD_REF=feature/local-test \
GITHUB_REF_NAME=develop \
CI_JDK_VERSION=openjdk21 \
CI_COMMIT_MESSAGE='PR dry run' \
bash cicd/gcviewer-script.sh

Option B: develop snapshot

JAVA_HOME=E:/swdevelopment/java/<selected-jdk> \
DRY_RUN=true \
GITHUB_EVENT_NAME=push \
GITHUB_REF_NAME=develop \
CI_JDK_VERSION=openjdk8 \
CI_COMMIT_MESSAGE='develop dry run' \
bash cicd/gcviewer-script.sh

Option C: master release

JAVA_HOME=E:/swdevelopment/java/<selected-jdk> \
DRY_RUN=true \
GITHUB_EVENT_NAME=push \
GITHUB_REF_NAME=master \
CI_JDK_VERSION=openjdk8 \
CI_COMMIT_MESSAGE='master dry run' \
GITHUB_TOKEN=dummy \
ENCRYPTION_PASSWORD=dummy \
GPG_DIR=cicd/gpg \
bash cicd/gcviewer-script.sh

5) Summarize route and proof

Report:

Which path ran:
- PR verification path
- develop snapshot path (dry-run deploy)
- master release path (dry-run release/push)
The selected JAVA_HOME
Key output lines proving DRY_RUN=true behavior.

---name: ci-script-only-rundescription: Simulate GCViewer CI paths (pull request, develop snapshot, master release) with DRY_RUN and selectable OpenJDK 8/17/21/25.---## What I do- Simulate GCViewer CI behavior locally without deploying.- Reproduce one of three CI paths: - pull request verification - develop snapshot (dry-run deploy path) - master release (dry-run release/push path)- Allow selecting Java runtime from: - `E:/swdevelopment/java/openjdk-8` - `E:/swdevelopment/java/openjdk-17` - `E:/swdevelopment/java/openjdk-21` - `E:/swdevelopment/java/openjdk-25`## When to use meUse this when you want a local CI-equivalent dry run of `cicd/gcviewer-script.sh` and a concise proof summary of the path taken and dry-run behavior.## Workflow### 1) Confirm repository and prerequisites- Verify current workspace is GCViewer repo root: - `git rev-parse --show-toplevel` - ensure `cicd/gcviewer-script.sh` exists- Verify required tools: - `bash --version` - `mvn -v`- If any prerequisite fails, stop and report the issue.### 2) Ask which CI dry run to simulateAsk:- `pull request`- `develop snapshot`- `master release`- `cancel`If user selects `cancel`, stop.### 3) Ask which JDK to useAsk:- `openjdk-8`- `openjdk-17`- `openjdk-21`- `openjdk-25`- `cancel`If user selects `cancel`, stop.Set:- `JAVA_HOME` = `E:/swdevelopment/java/<selected-jdk>`- `DRY_RUN=true` for all runs.### 4) Execute selected dry run via Git BashRun the appropriate command from the repo root. Replace `<selected-jdk>` with `openjdk-8`, `openjdk-17`, `openjdk-21`, or `openjdk-25`.#### Option A: pull request```bashJAVA_HOME=E:/swdevelopment/java/<selected-jdk> \DRY_RUN=true \GITHUB_EVENT_NAME=pull_request \GITHUB_HEAD_REF=feature/local-test \GITHUB_REF_NAME=develop \CI_JDK_VERSION=openjdk21 \CI_COMMIT_MESSAGE='PR dry run' \bash cicd/gcviewer-script.sh```#### Option B: develop snapshot```bashJAVA_HOME=E:/swdevelopment/java/<selected-jdk> \DRY_RUN=true \GITHUB_EVENT_NAME=push \GITHUB_REF_NAME=develop \CI_JDK_VERSION=openjdk8 \CI_COMMIT_MESSAGE='develop dry run' \bash cicd/gcviewer-script.sh```#### Option C: master release```bashJAVA_HOME=E:/swdevelopment/java/<selected-jdk> \DRY_RUN=true \GITHUB_EVENT_NAME=push \GITHUB_REF_NAME=master \CI_JDK_VERSION=openjdk8 \CI_COMMIT_MESSAGE='master dry run' \GITHUB_TOKEN=dummy \ENCRYPTION_PASSWORD=dummy \GPG_DIR=cicd/gpg \bash cicd/gcviewer-script.sh```### 5) Summarize route and proofReport:- Which path ran: - PR verification path - develop snapshot path (dry-run deploy) - master release path (dry-run release/push)- The selected `JAVA_HOME`- Key output lines proving `DRY_RUN=true` behavior.

Frequently asked questions

CI Script Only Run