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".
View on GitHubjeremylongshore/claude-code-plugins-plus-skills
groq-pack
plugins/saas-packs/groq-pack/skills/groq-ci-integration/SKILL.md
February 1, 2026
Select agents to install to:
npx add-skill https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/main/plugins/saas-packs/groq-pack/skills/groq-ci-integration/SKILL.md -a claude-code --skill groq-ci-integrationInstallation paths:
.claude/skills/groq-ci-integration/# Groq CI Integration
## Overview
Set up CI/CD pipelines for Groq integrations with automated testing.
## Prerequisites
- GitHub repository with Actions enabled
- Groq test API key
- npm/pnpm project configured
## Instructions
### Step 1: Create GitHub Actions Workflow
Create `.github/workflows/groq-integration.yml`:
```yaml
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
```
### Step 2: Configure Secrets
```bash
gh secret set GROQ_API_KEY --body "sk_test_***"
```
### Step 3: Add Integration Tests
```typescript
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');
});
});
```
## Output
- Automated test pipeline
- PR checks configured
- Coverage reports uploaded
- Release workflow ready
## Error Handling
| 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 |
## Examples
### Release Workflow
```yaml
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