perplexity-ci-integration
Configure Perplexity CI/CD integration with GitHub Actions and testing.Use when setting up automated testing, configuring CI pipelines,or integrating Perplexity tests into your build process.Trigger with phrases like "perplexity CI", "perplexity GitHub Actions","perplexity automated tests", "CI perplexity".
When & Why to Use This Skill
This Claude skill automates the configuration of Perplexity CI/CD integrations using GitHub Actions. It streamlines the setup of automated testing pipelines, manages secure API secrets via GitHub CLI, and establishes robust integration tests to ensure the reliability of Perplexity-powered features throughout the software development lifecycle.
Use Cases
- Automated Integration Testing: Automatically trigger Perplexity API connectivity and health checks on every pull request to prevent breaking changes in AI-dependent modules.
- Secure Secret Management: Streamline the configuration of Perplexity API keys across different environments using GitHub Secrets and automated CLI commands.
- Production Readiness Verification: Implement specialized release workflows that validate Perplexity integration performance and coverage before deploying to production environments.
| name | perplexity-ci-integration |
|---|---|
| description | | |
| allowed-tools | Read, Write, Edit, Bash(gh:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Perplexity CI Integration
Overview
Set up CI/CD pipelines for Perplexity integrations with automated testing.
Prerequisites
- GitHub repository with Actions enabled
- Perplexity test API key
- npm/pnpm project configured
Instructions
Step 1: Create GitHub Actions Workflow
Create .github/workflows/perplexity-integration.yml:
name: Perplexity Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_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
gh secret set PERPLEXITY_API_KEY --body "sk_test_***"
Step 3: Add Integration Tests
describe('Perplexity Integration', () => {
it.skipIf(!process.env.PERPLEXITY_API_KEY)('should connect', async () => {
const client = getPerplexityClient();
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
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
PERPLEXITY_API_KEY: ${{ secrets.PERPLEXITY_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Perplexity production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
Branch Protection
required_status_checks:
- "test"
- "perplexity-integration"
Resources
Next Steps
For deployment patterns, see perplexity-deploy-integration.