Skip to content
Back to skills

Groq Ci Integration

ASecurity

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".

  • 2,688 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 7, 2026
devopstypescriptbashnodetestinggitapici/cddocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill groq-ci-integration --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Groq Ci Integration?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Groq Ci Integration
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jeremylongshore-groq-ci-integration/badge)](https://www.skillsdirectory.com/skills/jeremylongshore-groq-ci-integration)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: groq-ci-integration
description: |
  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".
allowed-tools: Read, Write, Edit, Bash(gh:*)
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
---

# 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
      - run: npm run build
      - run: npm publish
```

### Branch Protection
```yaml
required_status_checks:
  - "test"
  - "groq-integration"
```

## Resources
- [GitHub Actions Documentation](https://docs.github.com/en/actions)
- [Groq CI Guide](https://docs.groq.com/ci)

## Next Steps
For deployment patterns, see `groq-deploy-integration`.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.