New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Qe Shift Left Testing

by proffesor-for-testing in proffesor-for-testing/agentic-qe

Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix.

MITAuto-check passedTesting & QA

Install Qe Shift Left Testing

skills CLI
$ npx skills add proffesor-for-testing/agentic-qe --skill qe-shift-left-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install proffesor-for-testing/agentic-qe qe-shift-left-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.kiro/skills/qe-shift-left-testing .claude/skills/qe-shift-left-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
qe-shift-left-testing
GitHub stars
494
Token cost
~1.5k tokens
SKILL.md length
292 words
Files
1
Skills in repo
111
Repo updated
First seen
Licence
MIT

At a glance

Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix.

  • Works in 5 steps: VALIDATE requirements before coding… → WRITE tests before implementation (TDD… → AUTOMATE in CI pipeline (every commit… → …
  • Implementing TDD
  • SKILL.md covers Quick Reference Card, Level 1: Tests in Every PR, Level 2: TDD Practice and Level 3: BDD in Refinement, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Qe Shift Left Testing is an agent skill from proffesor-for-testing/agentic-qe. Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Use when implementing TDD, CI/CD, or early quality practices.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering Test-driven development and CI/CD. The repository describes itself as: Agentic QE Fleet is an open-source AI-powered QA/QE platform designed for use with Coding Agents (works best with Claude Code) featuring specialized agents and skills to support… The licence is MIT.

When your agent uses it

  • Implementing TDD
  • Early quality practices

Example prompts

  • “/qe-shift-left-testing”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. VALIDATE requirements before coding (testability, BDD scenarios)
  2. WRITE tests before implementation (TDD red-green-refactor)
  3. AUTOMATE in CI pipeline (every commit triggers tests)
  4. FOLLOW test pyramid: Many unit (70%), some integration (20%), few E2E (10%)
  5. FIX defects immediately - never let them accumulate

What it can do on your machine

Read from SKILL.md and the folder at commit 829d030. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript, yaml, javascript and gherkin).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Qe Shift Left Testing loads about 1.5k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 292 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from proffesor-for-testing/agentic-qe at commit 829d030, republished under its MIT licence (© proffesor-for-testing). 292 words, ~1,470 tokens.

Download SKILL.mdSave it as .claude/skills/qe-shift-left-testing/SKILL.md (or your agent's skills folder).
name
qe-shift-left-testing
description
Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Use when implementing TDD, CI/CD, or early quality practices.
inclusion
auto
tags
shift-left, early-testing, tdd, bdd, ci-cd, prevention

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 red-green-refactor)
  3. AUTOMATE in CI pipeline (every commit triggers tests)
  4. FOLLOW test pyramid: Many unit (70%), some integration (20%), few E2E (10%)
  5. 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)

Critical Success Factors:

  • Defects found in requirements cost 1x; in production cost 100x
  • Every commit must run automated tests
  • Quality is built in, not tested in </default_to_action>

Quick Reference Card

When to Use
  • Reducing cost of defects
  • Implementing CI/CD pipelines
  • Starting TDD practice
  • Improving requirements quality
Cost of Defects by Phase
PhaseRelative CostExample
Requirements1xFix doc: 30 min
Design5xRedesign: few hours
Development10xCode fix: 1 day
Testing20xFix + retest: 2 days
Production100xHotfix + rollback + investigation
Test Pyramid
       /\        E2E (10%) - Critical user journeys
      /  \
     /    \      Integration (20%) - Component interactions
    /      \
   /________\    Unit (70%) - Fast, isolated, comprehensive
Shift-Left Levels
LevelPracticeWhen
1Unit tests in PRBefore merge
2TDDBefore implementation
3BDD/Example MappingDuring refinement
4Risk AnalysisDuring design

Level 1: Tests in Every PR

yaml
# 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

Level 2: TDD Practice

javascript
// Red: Write failing test first
test('calculates discount for orders over $100', () => {
  const order = new Order([{ price: 150 }]);
  expect(order.discount).toBe(15); // 10% off
});

// Green: Minimal implementation
class Order {
  get discount() {
    return this.total > 100 ? this.total * 0.1 : 0;
  }
}

// Refactor: Improve while keeping green

Level 3: BDD in Refinement

gherkin
# Example mapping before coding
Feature: Loyalty Discount
  Scenario: Gold member gets 15% discount
    Given a customer with "gold" membership
    When they checkout with $200 in cart
    Then discount applied is $30
    And order total is $170

  Scenario: New customer gets no discount
    Given a customer with no membership
    When they checkout with $200 in cart
    Then no discount is applied

Level 4: Risk Analysis in Design

typescript
// During architecture review
await Task("Risk Analysis", {
  phase: 'design',
  component: 'payment-service',
  questions: [
    'What happens when payment gateway times out?',
    'How do we handle duplicate submissions?',
    'What if inventory changed during checkout?'
  ]
}, "qe-requirements-validator");

// Output: Testability requirements, failure mode tests

Agent-Assisted Shift-Left

typescript
// 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
typescript
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'
});

Remember

Earlier = Cheaper. Requirements defects cost 1x; production defects cost 100x. Test pyramid: 70% unit, 20% integration, 10% E2E. Every commit runs tests. TDD builds quality in.

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

© proffesor-for-testing, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .kiro/skills/qe-shift-left-testing of proffesor-for-testing/agentic-qe.

Open the folder on GitHubat commit 829d030

Compare with similar skills

Qe Shift Left Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Qe Shift Left Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Qe Shift Left Testing this skillproffesor-for-testing/agentic-qe494—~1.5kAutomated safety check: PassMIT
Test Automatoraiskillstore/marketplace4308 repos~2.8kAutomated safety check: PassNone
Bats Shell Testing Patternswshobson/agents40k11 repos~1.3kAutomated safety check: PassMIT
Testingaiskillstore/marketplace4301 repos~2.9kAutomated safety check: PassNone
Ways Of Workingdevantler-tech/ksail166—~2kAutomated safety check: PassApache-2.0
Build Feature End To EndFerroxLabs/wayland608—~4kAutomated safety check: PassApache-2.0

Similar skills

  • Test Automator

    aiskillstore/marketplace

    Master AI-powered test automation with modern frameworks, self-healing tests, and comprehensive quality engineering.

    430 GitHub starsUsed in 8 repos~2.8k tokens
    Testing & QAAuto-check passed

  • Bats Shell Testing Patterns

    wshobson/agents

    Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.

    40k GitHub starsUsed in 11 repos~1.3k tokens
    Testing & QAAuto-check passed

  • Testing

    aiskillstore/marketplace

    Comprehensive testing specialization covering test strategy, automation, TDD methodology, test writing, and web app testing.

    430 GitHub starsUsed in 1 repo~2.9k tokens
    Testing & QAAuto-check passed

  • Ways Of Working

    devantler-tech/ksail

    Codifies devantler-tech engineering practices: agent-first development workflow, TDD, CI/CD pipelines, GitHub Flow, code quality gates, and Kubernetes workflows with ksail.

    166 GitHub stars~2k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Build Feature End To End

    FerroxLabs/wayland

    Orchestrates the full software feature development lifecycle from specification through production deployment, chaining five engineering skills into a cohesive build pipeline.

    608 GitHub stars~4k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • TDD

    fossasia/eventyay-interpretation

    Test-driven development. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 28 repos~1.1k tokens
    Testing & QAAuto-check passed

More from proffesor-for-testing/agentic-qe

All 111 skills in this repo

  • Contract Testing

    proffesor-for-testing/agentic-qe

    Consumer-driven contract testing for microservices using Pact, schema validation, API versioning, and backward compatibility testing.

    494 GitHub stars~1.8k tokensUpdated 3 days ago
    Auto-check passed

  • Mutation Testing

    proffesor-for-testing/agentic-qe

    Test quality validation through mutation testing, assessing test suite effectiveness by introducing code mutations and measuring kill rate.

    494 GitHub stars~1.7k tokensUpdated 3 days ago
    Auto-check passed

  • Performance Testing

    proffesor-for-testing/agentic-qe

    Profiles application performance under load using k6, Artillery, or JMeter to measure latency, throughput, and error rates.

    494 GitHub stars~2.4k tokensUpdated 3 days ago
    Auto-check passed

  • Code Review Quality

    proffesor-for-testing/agentic-qe

    Conduct context-driven code reviews focusing on quality, testability, and maintainability.

    494 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed

  • Security Testing

    proffesor-for-testing/agentic-qe

    Scans for security vulnerabilities including XSS, SQL injection, CSRF, and auth flaws using OWASP Top 10 methodology.

    494 GitHub stars~2.7k tokensUpdated 3 days ago
    Auto-check: notes

  • Database Testing

    proffesor-for-testing/agentic-qe

    Database schema validation, data integrity testing, migration testing, transaction isolation, and query performance.

    494 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed

Categories

Questions about Qe Shift Left Testing

What does Qe Shift Left Testing do?

Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix. Qe Shift Left Testing is an agent skill from proffesor-for-testing/agentic-qe. Move testing activities earlier in the development lifecycle to catch defects when they're cheapest to fix.

When should I use Qe Shift Left Testing?

Qe Shift Left Testing fits situations like: implementing TDD; early quality practices.

How do I install Qe Shift Left Testing in Claude Code?

Run `npx skills add proffesor-for-testing/agentic-qe --skill qe-shift-left-testing -a claude-code`. Or copy the skill folder (.kiro/skills/qe-shift-left-testing in proffesor-for-testing/agentic-qe) into .claude/skills/qe-shift-left-testing in your project. Claude Code loads it when a task matches its description.

How do I install Qe Shift Left Testing in Codex?

Run `npx skills add proffesor-for-testing/agentic-qe --skill qe-shift-left-testing -a codex`. Or copy the skill folder (.kiro/skills/qe-shift-left-testing in proffesor-for-testing/agentic-qe) into .agents/skills/qe-shift-left-testing in your project. Codex loads it when a task matches its description.

Can I use Qe Shift Left Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add proffesor-for-testing/agentic-qe --skill qe-shift-left-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/qe-shift-left-testing, .gemini/skills/qe-shift-left-testing, .github/skills/qe-shift-left-testing and .opencode/skills/qe-shift-left-testing in your project.

What does Qe Shift Left Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Qe Shift Left Testing is instructions for the agent only. Our summary lists: Node.js.

Does Qe Shift Left Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Qe Shift Left Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Qe Shift Left Testing use?

Qe Shift Left Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Qe Shift Left Testing use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Qe Shift Left Testing?

Skills that share tags, products or a category with Qe Shift Left Testing: Test Automator (aiskillstore/marketplace, 430 stars), Bats Shell Testing Patterns (wshobson/agents, 40k stars), Testing (aiskillstore/marketplace, 430 stars) and Ways Of Working (devantler-tech/ksail, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Qe Shift Left Testing?

proffesor-for-testing (a GitHub user) maintains it in proffesor-for-testing/agentic-qe, which has 494 GitHub stars. The repository holds 111 skills in this directory. The repository was last updated on October 4, 2026.

Source: proffesor-for-testing/agentic-qe on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.