From hex-pack
Configures Hex CI/CD integration with GitHub Actions — trigger project refreshes, set secrets, and run automated tests on deploy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hex-pack:hex-ci-integrationThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
```yaml
name: Deploy & Refresh Data
on:
push:
branches: [main]
jobs:
refresh-hex:
runs-on: ubuntu-latest
steps:
- name: Trigger Hex project refresh
env:
HEX_API_TOKEN: ${{ secrets.HEX_API_TOKEN }}
run: |
curl -X POST \
-H "Authorization: Bearer $HEX_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{"inputParams": {"triggered_by": "ci"}, "updateCacheResult": true}' \
https://app.hex.tech/api/v1/project/${{ vars.HEX_PROJECT_ID }}/run
gh secret set HEX_API_TOKEN --body "hex_token_..."
gh variable set HEX_PROJECT_ID --body "project-id"
npx claudepluginhub ia23a-lachnita/claude-code-plugins-plus-fix-skills --plugin hex-pack2plugins reuse this skill
First indexed Jul 17, 2026
Configure Hex CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Hex tests into your build process. Trigger with phrases like "hex CI", "hex GitHub Actions", "hex automated tests", "CI hex".
Provides GitHub Actions patterns for CI/CD pipelines, release automation with semantic-release, changesets, goreleaser, and testing strategies including matrix, cache, secrets, and reusable workflows.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.