From groq-pack
Configure Groq CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Groq tests into your build process. Trigger with phrases like "groq CI", "groq GitHub Actions", "groq automated tests", "CI groq".
How this skill is triggered — by the user, by Claude, or both
Slash command
/groq-pack:groq-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
Set up CI/CD pipelines for Groq integrations with automated testing.
Set up CI/CD pipelines for Groq integrations with automated testing.
Create .github/workflows/groq-integration.yml:
name: Groq Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
GROQ_API_KEY: ${{ secrets.GROQ_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
GROQ_API_KEY: ${{ secrets.GROQ_API_KEY }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run test:integration
gh secret set GROQ_API_KEY --body "sk_test_***"
describe('Groq Integration', () => {
it.skipIf(!process.env.GROQ_API_KEY)('should connect', async () => {
const client = getGroqClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via gh secret set |
| Tests timeout | Network issues | Increase timeout or mock |
| Auth failures | Invalid key | Check secret value |
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
GROQ_API_KEY: ${{ secrets.GROQ_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Groq production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
required_status_checks:
- "test"
- "groq-integration"
For deployment patterns, see groq-deploy-integration.
npx claudepluginhub aiminnovations/claude-code-plugins-plus --plugin groq-packGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
7plugins reuse this skill
First indexed Jul 11, 2026
Showing the 6 earliest of 7 plugins