Skip to main content
skill CX Codex

qe-quality-assessment — Claude Code skill: setup

qe-quality-assessment reviews code quality through complexity, lint, code smells, and test health. Use it for release scoring, quality gates, and deployment checks.

MIT 129 installs ★ 533 updated 2026-10-25

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add proffesor-for-testing/agentic-qe --skill qe-quality-assessment -a claude-code
Open on GitHub

What qe-quality-assessment does

The skill combines several quality views: code complexity, maintainability, duplication, test coverage, mutation score, vulnerabilities, technical debt, and documentation. It can apply pass, fail, and warn gates, calculate a score with grades from A to F, and produce recommendations for the codebase.

Its examples use aqe quality assess, aqe quality deploy-ready, aqe quality report, and aqe quality compare. The package also describes a quality analyzer, a deployment advisor, CI/CD output in report.json, and run history stored in run-history.json. Regenerability is warn-by-default, so that gate reports a concern without blocking the pipeline.

The listed platforms are Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Claude Code installation uses npx and the proffesor-for-testing/agentic-qe repository; the resulting skill file is placed at ~/.claude/skills/qe-quality-assessment/SKILL.md.

What it helps with

  • measure code complexity and maintainability
  • set CI quality gates with thresholds
  • judge whether a release is ready for production
  • compare quality across releases
  • build a scored quality report

Example prompts for the agent

  • Assess src/ for complexity, coverage, vulnerabilities, code smells, and technical debt, then return a quality score.
  • Check whether release v2.1.0 is ready for production and give a go/no-go recommendation from the test, security, performance, and documentation results.
  • Create a dashboard quality report for 30d, then compare releases v1.0 and v2.0.

How to install qe-quality-assessment

1Skills CLI (Vercel)

npx skills add proffesor-for-testing/agentic-qe --skill qe-quality-assessment -a claude-code

2Manually: put the files in place

~/.claude/skills/qe-quality-assessment/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/qe-quality-assessment/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about qe-quality-assessment

How do I install qe-quality-assessment in Claude Code?

Run npx skills add proffesor-for-testing/agentic-qe --skill qe-quality-assessment -a claude-code. The skill file will be available at ~/.claude/skills/qe-quality-assessment/SKILL.md.

What does qe-quality-assessment do?

It reviews code quality, applies quality gates, and checks release readiness. Its assessment combines code, testing, security, documentation, and technical-debt metrics into a report with a pass/fail result.

How does the regenerability gate work?

It combines mutation score with the durability tier backing a module. The warn mode reports a problem, while block can fail CI.

Source text

SKILL.md · MIT
---
name: "qe-quality-assessment"
description: "Evaluates code quality through complexity analysis, lint results, code smell detection, and test health metrics. Use when assessing deployment readiness, configuring quality gates, scoring a codebase for release, or generating quality reports with pass/fail verdicts."
trust_tier: 3
validation:
  schema_path: schemas/output.json
  validator_path: scripts/validate-config.json
  eval_path: evals/qe-quality-assessment.yaml
---

# QE Quality Assessment

## Purpose

Guide the use of v3's quality assessment capabilities including automated quality gates, metrics aggregation, trend analysis, and deployment readiness evaluation.

## Activation

- When evaluating code quality
- When setting up quality gates
- When assessing deployment readiness
- When tracking quality metrics
- When generating quality reports

## Quick Start

```bash
# Run quality assessment
aqe quality assess --scope src/ --gates all

# Check deployment readiness
aqe quality deploy-ready --environment production

# Generate quality report
aqe quality report --format dashboard --period 30d

# Compare quality between releases
aqe quality compare --from v1.0 --to v2.0
```

## Agent Workflow

```typescript
// Comprehensive quality assessment
Task("Assess code quality", `
  Evaluate quality for src/:
  - Code complexity (cyclomatic, cognitive)
  - Test coverage and mutation score
  - Security vulnerabilities
  - Code smells and technical debt
  - Documentation coverage
  Generate quality score and recommendations.
`, "qe-quality-analyzer")

// Deployment readiness check
Task("Check deployment readiness", `
  Evaluate if release v2.1.0 is ready for production:
  - All tests passing
  - Coverage thresholds met
  - No critical vulnerabilities
  - Performance benchmarks passed
  - Documentation updated
  Provide go/no-go recommendation.
`, "qe-deployment-advisor")
```

## Quality Dimensions

### 1. Code Quality Metrics

```typescript
await qualityAnalyzer.assessCode({
  scope: 'src/**/*.ts',
  metrics: {
    complexity: {
      cyclomatic: { max: 15, warn: 10 },
      cognitive: { max: 20, warn: 15 }
    },
    maintainability: {
      index: { min: 65 },
      duplication: { max: 3 }  // percent
    },
    documentation: {
      publicAPIs: { min: 80 },
      complexity: { min: 70 }
    }
  }
});
```

### 2. Quality Gates

```typescript
await qualityGate.evaluate({
  gates: {
    coverage: { min: 80, blocking: true },
    // Fault detection — coverage is necessary but NOT sufficient (ADR-113).
    // A suite can hit 90% coverage and catch no bugs; mutation score does not lie.
    mutationScore: { min: 0.6, blocking: false },   // warn-by-default; opt-in blocking
    regenerability: { min: 0.5, blocking: false },  // Deletion Test: durable oracle backing per module
    complexity: { max: 15, blocking: false },
    vulnerabilities: { critical: 0, high: 0, blocking: true },
    duplications: { max: 3, blocking: false },
    techDebt: { maxRatio: 5, blocking: false }
  },
  action: {
    onPass: 'proceed',
    onFail: 'block-merge',
    onWarn: 'notify'
  }
});
```

### 2a. Regenerability gate (ADR-113)

Coverage measures lines executed; **mutation score** measures whether the tests would
*notice a bug*, and **regenerability** answers the Deletion Test — "if this module were
deleted and regenerated, would a wrong rebuild be caught?" Regenerability = mutation
score discounted by the durability tier backing the module (durable > live > ephemeral
> none); ephemeral-only tests score low because they don't survive a reimplementation.

```typescript
import { evaluateRegenerabilityGate } from '../../../src/feedback/regenerability-gate.js';

const verdict = evaluateRegenerabilityGate(moduleProfiles, {
  mutationScoreMin: 0.6,
  regenerabilityMin: 0.5,
  mode: 'warn',   // 'block' to fail CI; warn-by-default so adoption never breaks pipelines
});
// verdict.passed (thresholds met) · verdict.blocking (should fail CI) · verdict.failures[]
```

Surface it next to coverage in reports: `Coverage 88% ✅ / Mutation 41% ⚠️ / Regenerability: ephemeral-only ⚠️`.

### 3. Deployment Readiness

```typescript
await deploymentAdvisor.assess({
  release: 'v2.1.0',
  criteria: {
    testing: {
      unitTests: 'all-pass',
      integrationTests: 'all-pass',
      e2eTests: 'critical-pass',
      performanceTests: 'baseline-met'
    },
    quality: {
      coverage: 80,
      noNewVulnerabilities: true,
      noRegressions: true
    },
    documentation: {
      changelog: true,
      apiDocs: true,
      releaseNotes: true
    }
  }
});
```

## Quality Score Calculation

```yaml
quality_score:
  components:
    test_coverage:
      weight: 0.25
      metrics: [statement, branch, function]

    code_quality:
      weight: 0.20
      metrics: [complexity, maintainability, duplication]

    security:
      weight: 0.25
      metrics: [vulnerabilities, dependencies]

    reliability:
      weight: 0.20
      metrics: [bug_density, flaky_tests, error_rate]

    documentation:
      weight: 0.10
      metrics: [api_coverage, readme, changelog]

  scoring:
    A: 90-100
    B: 80-89
    C: 70-79
    D: 60-69
    F: 0-59
```

## Quality Dashboard

```typescript
interface QualityDashboard {
  overallScore: number;  // 0-100
  grade: 'A' | 'B' | 'C' | 'D' | 'F';
  dimensions: {
    name: string;
    score: number;
    trend: 'improving' | 'stable' | 'declining';
    issues: Issue[];
  }[];
  gates: {
    name: string;
    status: 'pass' | 'fail' | 'warn';
    value: number;
    threshold: number;
  }[];
  trends: {
    period: string;
    scores: number[];
    alerts: Alert[];
  };
  recommendations: Recommendation[];
}
```

## CI/CD Integration

```yaml
# Quality gate in pipeline
quality_check:
  stage: verify
  script:
    - aqe quality assess --gates all --output report.json
  rules:
    - if: $CI_PIPELINE_SOURCE == "merge_request_event"
  artifacts:
    reports:
      quality: report.json
  allow_failure:
    exit_codes:
      - 1  # Warnings only
```

## Run History

After each quality assessment, append results to `run-history.json` in this skill directory:
```bash
node -e "
const fs = require('fs');
const h = JSON.parse(fs.readFileSync('.claude/skills/qe-quality-assessment/run-history.json'));
h.runs.push({date: new Date().toISOString().split('T')[0], gate_result: 'PASS_OR_FAIL', failed_checks: []});
fs.writeFileSync('.claude/skills/qe-quality-assessment/run-history.json', JSON.stringify(h, null, 2));
"
```
Read `run-history.json` before each run — alert if quality gate failed 3 of last 5 runs.

## Skill Composition

- **Before assessment** → Run `/qe-coverage-analysis` and `/mutation-testing` first
- **If issues found** → Use `/test-failure-investigator` to diagnose failures
- **For PR review** → Combine with `/code-review-quality` for comprehensive review

## Gotchas

- NEVER trust agent-reported pass/fail status — 12 test failures were caught that agents claimed were passing (Nagual pattern, reward 0.92)
- Completion theater: agent hardcoded version '3.0.0' instead of reading from package.json — verify actual values in output
- Fix issues in priority waves (P0 → P1 → P2) with verification between each wave — don't fix everything in parallel
- quality-assessment domain has 53.7% success rate — expect failures and have fallback
- If HybridMemoryBackend initialization fails, run `aqe health` to diagnose, or `aqe init` to re-initialize

## Coordination

**Primary Agents**: qe-quality-analyzer, qe-deployment-advisor, qe-metrics-collector
**Coordinator**: qe-quality-coordinator
**Related Skills**: qe-coverage-analysis, security-testing

© proffesor-for-testing · MIT · proffesor-for-testing/agentic-qe

Similar skills

All skills for Testing and QA →

From the same set73

The whole set →
wms-testing-patterns wms-testing-patterns is a Claude Code skill with patterns for testing inventory accuracy, pick waves, EDI documents, and WMS-ERP integration. CX Codex +1 134installs six-thinking-hats Applies Six Thinking Hats to test strategy, failure analysis, and retrospectives. It separates facts, risks, benefits, ideas, feelings, and next actions. CX Codex +1 131installs a11y-ally The a11y-ally skill audits pages for WCAG issues and suggests fixes based on page context. Use it to review a site or assess video accessibility. CX Codex +1 131installs contract-testing Guides consumer-driven contract testing for microservices using Pact, catching breaking API changes before deploy. CX Codex +1 130installs qe-defect-intelligence qe-defect-intelligence identifies high-risk code before bugs escape by analyzing change frequency, complexity metrics, and past defect patterns. Flags risky PRs and runs root cause analysis on test failures. CX Codex +1 129installs risk-based-testing risk-based-testing directs QA effort to high-risk areas using a 1-5 probability and impact scale, adjusting test depth dynamically. CX Codex +1 128installs n8n-trigger-testing-strategies n8n-trigger-testing-strategies — a skill for testing how n8n workflows get triggered: webhooks, cron schedules, service events, polling. Useful when a workflow fires at the wrong moment or not at all. CX Codex +1 128installs n8n-expression-testing n8n-expression-testing is a Claude Code skill that checks n8n expressions against different data contexts, including missing values, while debugging data transformations. CX Codex +1 127installs

Project sponsors

Companies that keep this analytics open