From deepgram-pack
Configure Deepgram CI/CD integration for automated testing and deployment. Use when setting up continuous integration pipelines, automated testing, or deployment workflows for Deepgram integrations. Trigger with phrases like "deepgram CI", "deepgram CD", "deepgram pipeline", "deepgram github actions", "deepgram automated testing".
How this skill is triggered — by the user, by Claude, or both
Slash command
/deepgram-pack:deepgram-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
- [Overview](#overview)
Set up continuous integration and deployment pipelines for Deepgram integrations. Covers GitHub Actions, GitLab CI, integration test suites, smoke tests, and automated key rotation.
Store DEEPGRAM_API_KEY and DEEPGRAM_PROJECT_ID as CI/CD secrets. Use separate keys per environment.
Set up automated testing on push/PR with unit tests, linting, and type checking.
Implement Deepgram-specific integration tests: API connectivity, pre-recorded transcription, language detection, and error handling.
Set up staged deployment: test -> lint -> integration -> staging deploy -> smoke test.
Configure monthly automated key rotation via gh secret set in a scheduled workflow.
| Issue | Cause | Resolution |
|---|---|---|
| Integration tests fail | Invalid or expired API key | Rotate DEEPGRAM_API_KEY secret |
| Smoke test timeout | API latency or network issues | Increase timeout, check status page |
| Build fails | Missing dependencies | Verify npm ci succeeds |
DEEPGRAM_API_KEY=xxx npx tsx scripts/smoke-test.ts
Tests API connectivity and transcription of the NASA podcast sample, exits non-zero on failure.
{
"test:integration": "vitest run --config vitest.integration.config.ts",
"test:deepgram": "vitest run tests/integration/deepgram.test.ts",
"smoke-test": "tsx scripts/smoke-test.ts"
}
See detailed implementation for advanced patterns.
npx claudepluginhub terrylica/claude-code-plugins-plus --plugin deepgram-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.
4plugins reuse this skill
First indexed Jul 11, 2026