tests-as-context

Enrich semantic code search results with DSL test chunks and git-based stability signals.

11|3|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill tests-as-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tests-as-context
Source: https://github.com/artk0de/TeaRAGs-MCP/tree/main/.claude-plugin/tea-rags/skills/tests-as-context
Command: npx skills add https://github.com/artk0de/TeaRAGs-MCP --skill tests-as-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the issue of agents lacking visibility into the stability and history of code, preventing them from relying on buggy or unverified examples during development.

Core Features & Use Cases

  • Test-Driven Enrichment: Surfaces relevant test scenarios and fixtures directly into the agent's context for refactoring, debugging, and verification.
  • Regression Archaeology: Identifies when specific feature contracts were introduced to help understand the evolution of a codebase.
  • Flakiness Detection: Highlights unstable test zones and infrastructure that frequently break, allowing agents to avoid unreliable patterns.

Quick Start

Ask the agent to identify tests at risk for the current file changes to ensure your refactoring remains verified.

Frequently Asked Questions about tests-as-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enrich code search results with relevant test scenarios for refactoring?

Code search enrichment surfaces DSL test chunks and git-based stability signals directly into agent context. It filters test-related code chunks based on authorship, churn, and bug-fix rates to ensure refactoring relies on verified scenarios.

What is test-driven context enrichment and how does it help prevent regressions?

Test-driven context enrichment is the process of injecting battle-tested scenarios and fixtures into development context. It highlights unstable test zones and identifies when feature contracts were introduced to prevent relying on buggy examples.

Can I detect flaky tests and unstable infrastructure using git history and code search?

Yes, flakiness detection identifies unstable test zones and infrastructure that frequently break. It analyzes git-based stability signals and bug-fix rates to highlight unreliable patterns so agents can avoid them during development.

Does semantic code search work with TeaRAGs MCP server for TDD workflows?

Semantic code search requires integration with the TeaRAGs MCP server to filter and rank test-related code chunks. This combination provides the necessary context for refactoring, verification, and TDD workflows across diverse language domains.

What's the best way to check if my current file changes put existing tests at risk?

The best way is to ask the agent to identify tests at risk for the current file changes. This ensures your refactoring remains verified by surfacing relevant regression scenarios and stability signals from the codebase history.