gamma-ci-integration
Configure Gamma CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Gamma tests into your build process. Trigger with phrases like "gamma CI", "gamma GitHub Actions", "gamma automated tests", "CI gamma", "gamma pipeline".
What this skill does
# Gamma CI Integration
## Overview
Set up continuous integration for Gamma-powered applications with automated testing and deployment.
## Prerequisites
- GitHub repository with Actions enabled
- Gamma test API key
- npm/pnpm project configured
## Instructions
### Step 1: Create GitHub Actions Workflow
```yaml
# .github/workflows/gamma-ci.yml
name: Gamma CI
on:
push:
branches: [main, develop]
pull_request:
branches: [main]
env:
GAMMA_API_KEY: ${{ secrets.GAMMA_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci
- name: Run unit tests
run: npm test
- name: Run Gamma integration tests
run: npm run test:gamma
env:
GAMMA_MOCK: ${{ github.event_name == 'pull_request' }}
- name: Upload coverage
uses: codecov/codecov-action@v4
with:
files: ./coverage/lcov.info
```
### Step 2: Create Test Scripts
```json
// package.json
{
"scripts": {
"test": "vitest run",
"test:gamma": "vitest run --config vitest.gamma.config.ts",
"test:gamma:live": "GAMMA_MOCK=false vitest run --config vitest.gamma.config.ts"
}
}
```
### Step 3: Gamma Test Configuration
```typescript
// vitest.gamma.config.ts
import { defineConfig } from 'vitest/config';
export default defineConfig({
test: {
include: ['tests/gamma/**/*.test.ts'],
testTimeout: 60000, // Gamma API can be slow # 60000: 1 minute in ms
hookTimeout: 30000, # 30000: 30 seconds in ms
setupFiles: ['./tests/gamma/setup.ts'],
},
});
```
### Step 4: Test Setup with Mocking
```typescript
// tests/gamma/setup.ts
import { beforeAll } from 'vitest';
import { createGammaClient, type GammaClient } from '../../src/client';
const useMock = process.env.GAMMA_MOCK === 'true';
export let gamma: ReturnType<typeof createGammaClient>;
beforeAll(() => {
if (useMock) {
gamma = createMockGammaClient();
} else {
gamma = createGammaClient({
apiKey: process.env.GAMMA_API_KEY!,
});
}
});
function createMockGammaClient() {
return {
generate: vi.fn().mockResolvedValue({ generationId: 'mock-gen-id' }),
poll: vi.fn().mockResolvedValue({
status: 'completed',
gammaUrl: 'https://gamma.app/docs/mock-test',
exportUrl: 'https://export.gamma.app/mock.pdf',
creditsUsed: 10,
}),
listThemes: vi.fn().mockResolvedValue([{ id: 'theme_1', name: 'Default' }]),
listFolders: vi.fn().mockResolvedValue([]),
};
}
```
### Step 5: Integration Test Example
```typescript
// tests/gamma/generation.test.ts
import { describe, it, expect } from 'vitest';
import { gamma } from './setup';
describe('Gamma Generation', () => {
it('should start a generation', async () => {
const result = await gamma.generate({
content: 'CI Test: 1-card overview of testing',
outputFormat: 'presentation',
});
expect(result.generationId).toBeDefined();
});
it('should list workspace themes', async () => {
const themes = await gamma.listThemes();
expect(Array.isArray(themes)).toBe(true);
});
});
```
### Step 6: Add Secrets to GitHub
```bash
# Using GitHub CLI
gh secret set GAMMA_API_KEY --body "your-test-api-key"
# Verify secrets
gh secret list
```
## Output
- Automated test pipeline running on push/PR
- Mock mode for PR checks (no API calls)
- Live integration tests on main branch
- Coverage reports uploaded
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| Secret not found | Missing GitHub secret | Add GAMMA_API_KEY secret |
| Test timeout | Slow API response | Increase testTimeout |
| Mock mismatch | Mock out of sync | Update mock responses |
| Rate limit in CI | Too many test runs | Use mock mode for PRs |
## Resources
- [GitHub Actions Documentation](https://docs.github.com/en/actions)
- [Vitest Documentation](https://vitest.dev/)
- [Gamma Testing Guide](https://gamma.app/docs/testing)
## Next Steps
Proceed to `gamma-deploy-integration` for deployment workflows.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.