Agent skill

langfuse-ci-integration

Configure Langfuse CI/CD integration with GitHub Actions and automated testing. Use when setting up automated testing, configuring CI pipelines, or integrating Langfuse tests into your build process. Trigger with phrases like "langfuse CI", "langfuse GitHub Actions", "langfuse automated tests", "CI langfuse", "langfuse pipeline". '

intentsolutions.io2,596★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-ci-integration --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 9 KB
Bundled scripts: none
Version: 1.12.0
Declared author: Jeremy Longshore <jeremy@intentsolutions.io>
Allowed tools: ReadWriteEditBash(gh:*)
Requires: Designed for Claude Code, also compatible with Codex and OpenClaw
Path: plugins/saas-packs/langfuse-pack/skills/langfuse-ci-integration/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,630
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Langfuse CI Integration ## Overview Integrate Langfuse into CI/CD pipelines: trace validation tests, prompt regression testing, experiment-driven quality gates, automated prompt deployment from version control, and score monitoring. ## Prerequisites - Langfuse API keys stored as GitHub secrets (`LANGFUSE_PUBLIC_KEY`, `LANGFUSE_SECRET_KEY`) - Test framework (Vitest or Jest) - OpenAI API key for LLM tests ## Instructions ### Step 1: GitHub Actions Workflow for AI Quality Tests ```yaml # .github/workflows/langfuse-tests.yml name: AI Quality Tests on: pull_request: paths: ["src/ai/**", "src/prompts/**", "tests/ai/**"] jobs: ai-quality: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: { node-version: "20", cache: "npm" } - run: npm ci - name: Run AI quality tests with tracing env: LANGFUSE_PUBLIC_KEY: ${{ secrets.LANGFUSE_PUBLIC_KEY }} LANGFUSE_SECRET_KEY: ${{ secrets.LANGFUSE_SECRET_KEY }} LANGFUSE_BASE_URL: ${{ vars.LANGFUSE_BASE_URL || 'https://cloud.langfuse.com' }} OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }} run: npx vitest run tests/ai/ --reporter=verbose - name: Langfuse connectivity check env: LANGFUSE_PUBLIC_KEY: ${{ secrets.LANG

What's inside
Steps it walks through
  1. Overview
  2. Prerequisites
  3. Instructions
  4. Step 1: GitHub Actions Workflow for AI Quality Tests
  5. Step 2: Prompt Regression Tests
  6. Step 3: Experiment-Driven Quality Gates
  7. Step 4: Automated Prompt Deployment
  8. Step 5: Score Regression Monitoring
  9. CI Best Practices
  10. Error Handling
  11. Resources
More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the langfuse-ci-integration skill do?

Configure Langfuse CI/CD integration with GitHub Actions and automated testing. Use when setting up automated testing, configuring CI pipelines, or integrating Langfuse tests into your build process. Trigger with phrases like "langfuse CI", "langfuse GitHub Actions", "langfuse automated tests", "CI langfuse", "langfuse pipeline". '

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill langfuse-ci-integration --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,630 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going