Quality Standards

VerifiedSafe

Reference for protected quality thresholds and quality tool commands. Use it to understand required metrics, run comprehensive checks, or determine which specialized skill to invoke for fixing violations. Helps maintain strict quality gates before commits.

Sby Skills Guide Bot
TestingBeginner
6/2/2026
Claude Code
#quality-thresholds#phpinsights#deptrac#psalm#infection

Recommended for

Automated summary

Provides an overview of protected quality thresholds and commands for comprehensive quality checks, routing users to specialized skills for fixing issues.

Strengths

  • Centralizes all quality metrics in one reference.
  • Clearly specifies which skills to use for violations.
  • Provides quick commands for CI checks.
  • Covers multiple tools (PHPInsights, Deptrac, Psalm, Infection, PHPUnit).

Limitations

  • Does not perform fixes itself; relies on other skills.
  • May become outdated if thresholds change.
  • Only covers PHP stack (implicitly).
When to use it

Use when you need to understand the required quality levels before committing or when you need to identify which specialized skill addresses a specific quality issue.

When not to use it

Do not use for actually fixing quality issues; instead use the dedicated skills like deptrac-fixer, complexity-management, or testing-workflow.

Security analysis

Safe
Quality score95/100

This skill is purely informational, providing reference tables of quality thresholds and commands (all standard make targets) without any destructive or exfiltrating instructions. No code execution, network calls, or safety bypasses are involved.

No concerns found

How this analysis is made

Examples

Check quality thresholds
I need to see the protected quality thresholds for our PHP project before I commit. Show me the required percentages for PHPInsights and other tools.
Run comprehensive checks
Run all CI quality checks before commit. What command should I use?
Route to fix tool
PHPInsights shows a complexity violation. Which skill should I use to fix it?

name: quality-standards description: Overview of protected quality thresholds and quick reference for all quality tools. Use when you need to understand quality metrics, run comprehensive quality checks, or learn which specialized skill to use. For specific issues, use dedicated skills (deptrac-fixer for Deptrac, complexity-management for PHPInsights, testing-workflow for coverage).

Quality Standards Skill

Context (Input)

  • Need to understand protected quality thresholds
  • Running comprehensive quality checks before commit
  • Determining which specialized skill to use for specific issues
  • Quick reference for quality tool commands

Task (Function)

Understand quality metrics and route to appropriate specialized skill for fixes.

Success Criteria: Know which skill to use for your specific quality issue.

Protected Quality Thresholds

CRITICAL: These thresholds are protected and must NEVER be lowered.

PHPInsights (Source Code)

| Metric | Required | Fix With | | ------------ | -------- | ---------------------------------------------------------- | | Quality | 100% | complexity-management | | Complexity | 94% | complexity-management | | Architecture | 100% | deptrac-fixer | | Style | 100% | Run make phpcsfixer |

PHPInsights (Tests)

| Metric | Required | Fix With | | ------------ | -------- | ---------------------------------------------------------- | | Quality | 95% | complexity-management | | Complexity | 95% | complexity-management | | Architecture | 90% | deptrac-fixer | | Style | 95% | Run make phpcsfixer |

Other Tools

| Tool | Metric | Required | Fix With | | --------- | --------------- | -------- | ------------------------------------------------ | | Deptrac | Violations | 0 | deptrac-fixer | | Psalm | Errors | 0 | Fix reported issues | | Psalm | Security Issues | 0 | Fix tainted flows | | Infection | MSI | 100% | testing-workflow | | PHPUnit | Coverage | 100% | testing-workflow |

Quick Reference Commands

Comprehensive Checks

# Run all CI checks (recommended before commit)
make ci

Success: Must output "✅ CI checks successfully passed!"

Individual Quality Checks

| Check | Command | Purpose | | ------------------- | ------------------------ | ---------------------------- | | Code quality | make phpinsights | All PHPInsights metrics | | Complexity analysis | make phpmd | Find high-complexity methods | | Static analysis | make psalm | Type checking and errors | | Security taint | make psalm-security | Security vulnerability scan | | Architecture | make deptrac | Layer boundary validation | | Code style | make phpcsfixer | Auto-fix PSR-12 style | | Composer validation | make composer-validate | Validate composer.json |

Testing Commands

| Check | Command | Purpose | | ----------------- | -------------------------- | --------------------------- | | Unit tests | make unit-tests | Domain/Application logic | | Integration tests | make integration-tests | Component interactions | | E2E tests | make behat | Full user scenarios (Behat) | | All tests | make all-tests | Unit + Integration + E2E | | Test coverage | make tests-with-coverage | Generate coverage report | | Mutation tests | make infection | Test quality validation |

Routing to Specialized Skills

When quality checks fail, use the appropriate specialized skill:

Architecture Issues

  • Deptrac violations → deptrac-fixer

    • Domain depends on Infrastructure
    • Layer boundary violations
    • "must not depend on" errors
  • DDD architecture patterns → implementing-ddd-architecture

    • Creating new entities/value objects
    • Implementing CQRS patterns
    • Understanding layer responsibilities

Code Quality Issues

  • High cyclomatic complexity → complexity-management

    • PHPInsights complexity < 94%
    • PHPMD reports high CCN
    • Methods too complex
  • Code style issues → Run make phpcsfixer

    • PSR-12 violations
    • Line length > 100 chars
    • Formatting issues

Testing Issues

  • Test failures → testing-workflow
    • Unit/Integration/E2E failures
    • Mutation testing (Infection)
    • Test coverage < 100%

Workflow Integration

  • Before committing → ci-workflow

    • Run all checks systematically
    • Fix failures in priority order
    • Ensure all checks pass
  • PR review feedback → code-review

    • Fetch and address PR comments
    • Systematic comment resolution

Quality Improvement Workflow

Step 1: Run Comprehensive Checks

make ci

Step 2: Identify Failing Check

Check output for specific failure:

❌ CI checks failed:
  - phpinsights: Complexity score too low (93.5% < 94%)

Step 3: Use Specialized Skill

Based on failure type, use appropriate skill:

| Failure Pattern | Skill to Use | | -------------------------- | ------------------------ | | "Complexity score too low" | complexity-management | | "Deptrac violations" | deptrac-fixer | | "must not depend on" | deptrac-fixer | | "tests failed" | testing-workflow | | "Psalm found errors" | Fix type errors directly | | "escaped mutants" | testing-workflow |

Step 4: Re-run CI

make ci

Repeat until: "✅ CI checks successfully passed!"

Constraints (Parameters)

NEVER

  • Lower quality thresholds in config files (phpinsights.php, infection.json5, etc.)
  • Skip failing checks to "save time"
  • Commit code without all CI checks passing
  • Modify deptrac.yaml to allow violations (fix code, not config)
  • Disable security checks

ALWAYS

  • Fix code to meet standards (not config to meet code)
  • Run make ci before creating commits
  • Use specialized skills for specific quality issues
  • Maintain 100% test coverage
  • Keep cyclomatic complexity low (target: < 5 per method)
  • Respect hexagonal architecture boundaries

Format (Output)

Expected CI Output

✅ CI checks successfully passed!

Expected PHPInsights Output

[CODE] 100.0 pts       ✅ Target: 100%
[COMPLEXITY] 94.0 pts  ✅ Target: 94%
[ARCHITECTURE] 100 pts ✅ Target: 100%
[STYLE] 100.0 pts      ✅ Target: 100%

Expected Deptrac Output

✅ No violations found

Expected Infection Output

Mutation Score Indicator (MSI): 100%

Verification Checklist

After using this skill:

  • [ ] Identified which quality check is failing
  • [ ] Selected appropriate specialized skill for the issue
  • [ ] Ready to execute specialized skill workflow
  • [ ] Understand which threshold applies to the failure
  • [ ] Know the command to re-run the check after fixes

Related Skills

Reference Documentation

For detailed examples and patterns, see:

  • Refactoring patterns → complexity-management skill
  • Architecture rules → implementing-ddd-architecture skill
  • Layer boundaries → deptrac-fixer skill
  • Testing strategies → testing-workflow skill

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/quality-standards-mm5t89xb/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/quality-standards-mm5t89xb' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/quality-standards-mm5t89xb/download' --output '.skill-downloads/quality-standards-mm5t89xb/SKILL.md.part' && mv '.skill-downloads/quality-standards-mm5t89xb/SKILL.md.part' '.skill-downloads/quality-standards-mm5t89xb/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/quality-standards-mm5t89xb/SKILL.md' && test -s '.skill-downloads/quality-standards-mm5t89xb/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/quality-standards' && cp -R '.skill-downloads/quality-standards-mm5t89xb' '.claude/skills/quality-standards'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/quality-standards-mm5t89xb'

openskills read 'quality-standards-mm5t89xb'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/quality-standards-mm5t89xb/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills