Agent skill · software engineering · jeremylongshore
groq-ci-integration
Configure Groq CI/CD integration with GitHub Actions, testing, and model
Why this skill is useful
Adds a complete CI/CD integration setup for Groq with executable YAML workflows and testing scripts that aren't publicly documented.
What it needs
Requires gh installed locally. Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Groq CI Integration Overview Set up CI/CD pipelines for Groq integrations with unit tests (mocked), integration tests (live API), and model deprecation checks. Groq's fast inference makes live integration tests practical in CI -- a completion round-trip takes < 500ms. Prerequisites GitHub repository with Actions enabled Groq API key stored as GitHub secret vitest or jest for testing Instructions The integration has four moving parts. Read this section for the high-level flow, then drill into the reference files for the full copy-paste blocks — the complete workflows and configuration live in references/implementation.md and the full test suite in references/examples.md. Step 1: GitHub Actions workflow Write .github/workflows/groq-tests.yml with three jobs: unit-tests (mocked groq-sdk, runs on every PR, no key), integration-tests (live API, push-to-main only, guarded by if: github.eventname != 'pullrequest'), and a weekly model-check cron that diffs the model IDs the code references against Groq's live model list. The job skeleton: Step 2: Configure secrets Store a CI-scoped key with gh secret set GROQAPIKEY --body "gskyourcikeyhere". Keep it separate from the production key so it rotates and tracks CI usage independently. Step 3: Integration test suite Add tests/groq.integration.ts gated on a GROQINTEGRATION env var (so the file is a no-op without a key). It asserts model listing, chat completion, streaming, and JSON mode. Full file: references/examples.md. Step 4: Release workflow Gate npm publish behind a live production Groq round-trip so a broken key or deprecated model blocks the release. Full release.yml: references/implementation.md. CI best practices: mock groq-sdk in unit tests, run integration tests only on main push (saves quota), prefer llama-3.1-8b-instant (cheapest, fastest) with low maxtokens (5-50), add timeout-minutes: 2, and schedule the weekly deprecation check. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/groq-ci-integration