Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
proffesor-for-testing avatar

Shift Left Testing

  • 94 installs
  • 433 repo stars
  • Updated August 4, 2026
  • proffesor-for-testing/agentic-qe

shift-left-testing is a Claude Code skill for testing & qa.

About

shift-left-testing is a Claude Code skill for testing & qa. It helps solo builders move faster with AI-assisted development.

  • shift-left-testing
  • Testing & QA
  • AI-coding skill

Shift Left Testing by the numbers

  • 94 all-time installs (skills.sh)
  • +3 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #1,019 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/proffesor-for-testing/agentic-qe --skill shift-left-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs94
repo stars433
Last updatedAugust 4, 2026
Repositoryproffesor-for-testing/agentic-qe

How do I helps with testing & qa tasks.?

Helps with testing & qa tasks.

Who is it for?

Best when you're working on testing & qa and need structured help with shift left testing.

Skip if: Teams with no testing & qa needs, or anyone wanting a generic chat assistant without this specific workflow.

When should I use this skill?

When you need to helps with testing & qa tasks., or when shift-left-testing is a claude code skill for testing & qa.

What you get

Structured output aligned to shift-left-testing: shift-left-testing, Testing & QA.

Files

SKILL.mdMarkdownGitHub ↗

Shift-Left Testing

<default_to_action> When implementing early testing practices: 1. VALIDATE requirements before coding (testability, BDD scenarios) 2. WRITE tests before implementation (TDD) 3. AUTOMATE in CI pipeline (every commit triggers tests) 4. FIX defects immediately - never let them accumulate

Quick Shift-Left Levels:

  • Level 1: Unit tests with each PR (developer responsibility)
  • Level 2: TDD practice (tests before code)
  • Level 3: BDD/Example mapping in refinement (requirements testing)
  • Level 4: Risk analysis in design (architecture testing)

</default_to_action>

Quick Reference Card

When to Use

  • Reducing cost of defects
  • Implementing CI/CD pipelines
  • Starting TDD practice
  • Improving requirements quality

Shift-Left Levels

LevelPracticeWhen
1Unit tests in PRBefore merge
2TDDBefore implementation
3BDD/Example MappingDuring refinement
4Risk AnalysisDuring design

---

Level 1: Tests in Every PR

# CI pipeline - tests run on every commit
name: CI
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npm run test:unit
      - run: npm run test:integration
      - run: npm run lint

  quality-gate:
    needs: test
    steps:
      - name: Coverage Check
        run: npx coverage-check --min 80
      - name: No New Warnings
        run: npm run lint -- --max-warnings 0

---

Agent-Assisted Shift-Left

// Validate requirements testability
await Task("Requirements Validation", {
  requirements: userStories,
  check: ['INVEST-criteria', 'testability', 'ambiguity'],
  generateBDD: true
}, "qe-requirements-validator");

// Generate tests from requirements
await Task("Generate Tests", {
  source: 'requirements',
  types: ['unit', 'integration', 'e2e'],
  coverage: 'comprehensive'
}, "qe-test-generator");

// Smart test selection for changes
await Task("Select Regression Tests", {
  changedFiles: prFiles,
  algorithm: 'risk-based',
  targetReduction: 0.7  // 70% time savings
}, "qe-regression-risk-analyzer");

---

Agent Coordination Hints

Memory Namespace

aqe/shift-left/
├── requirements/*       - Validated requirements
├── generated-tests/*    - Auto-generated tests
├── coverage-targets/*   - Coverage goals by component
└── pipeline-results/*   - CI/CD test history

Fleet Coordination

const shiftLeftFleet = await FleetManager.coordinate({
  strategy: 'shift-left',
  agents: [
    'qe-requirements-validator',     // Level 3-4
    'qe-test-generator',             // Level 2
    'qe-regression-risk-analyzer'    // Smart selection
  ],
  topology: 'sequential'
});

---

Related Skills

  • tdd-london-chicago - TDD practices
  • holistic-testing-pact - Proactive testing
  • cicd-pipeline-qe-orchestrator - Pipeline integration
  • shift-right-testing - Production feedback

---

Remember

With Agents: Agents validate requirements testability, generate tests from specs, and select optimal regression suites. Use agents to implement shift-left practices consistently.

Skill Composition

  • TDD practice → Use /tdd-london-chicago for specific TDD guidance
  • Generate tests → Use /qe-test-generation for AI-powered test generation
  • CI/CD quality → Use /cicd-pipeline-qe-orchestrator for pipeline setup

Gotchas

  • "Shift left" doesn't mean "only test left" — production monitoring (shift right) is still needed
  • Agent generates tests before understanding requirements — tests for wrong behavior are worse than no tests
  • CI pipeline tests that take >10 minutes kill the feedback loop — keep commit-stage tests under 5 minutes
  • TDD discipline degrades when agent writes test+code simultaneously — enforce Red phase separation
  • Shifting left without lightweight environments just shifts the bottleneck — fix environments first

Related skills

FAQ

What does shift-left-testing do?

shift-left-testing is a Claude Code skill for testing & qa.

When should I use shift-left-testing?

When you need to helps with testing & qa tasks., or when shift-left-testing is a claude code skill for testing & qa.

What are the main capabilities?

shift-left-testing; Testing & QA; AI-coding skill.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.