quality-standards

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).

16 stars

Best use case

quality-standards is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

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).

Teams using quality-standards should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/quality-standards/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/testing-security/quality-standards/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/quality-standards/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How quality-standards Compares

Feature / Agentquality-standardsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

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).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# 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-management/SKILL.md) |
| Complexity   | 94%      | [complexity-management](../complexity-management/SKILL.md) |
| Architecture | 100%     | [deptrac-fixer](../deptrac-fixer/SKILL.md)                 |
| Style        | 100%     | Run `make phpcsfixer`                                      |

### PHPInsights (Tests)

| Metric       | Required | Fix With                                                   |
| ------------ | -------- | ---------------------------------------------------------- |
| Quality      | 95%      | [complexity-management](../complexity-management/SKILL.md) |
| Complexity   | 95%      | [complexity-management](../complexity-management/SKILL.md) |
| Architecture | 90%      | [deptrac-fixer](../deptrac-fixer/SKILL.md)                 |
| Style        | 95%      | Run `make phpcsfixer`                                      |

### Other Tools

| Tool      | Metric          | Required | Fix With                                         |
| --------- | --------------- | -------- | ------------------------------------------------ |
| Deptrac   | Violations      | 0        | [deptrac-fixer](../deptrac-fixer/SKILL.md)       |
| Psalm     | Errors          | 0        | Fix reported issues                              |
| Psalm     | Security Issues | 0        | Fix tainted flows                                |
| Infection | MSI             | 100%     | [testing-workflow](../testing-workflow/SKILL.md) |
| PHPUnit   | Coverage        | 100%     | [testing-workflow](../testing-workflow/SKILL.md) |

## Quick Reference Commands

### Comprehensive Checks

```bash
# 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](../deptrac-fixer/SKILL.md)

  - Domain depends on Infrastructure
  - Layer boundary violations
  - "must not depend on" errors

- **DDD architecture patterns** → [implementing-ddd-architecture](../implementing-ddd-architecture/SKILL.md)
  - Creating new entities/value objects
  - Implementing CQRS patterns
  - Understanding layer responsibilities

### Code Quality Issues

- **High cyclomatic complexity** → [complexity-management](../complexity-management/SKILL.md)

  - 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](../testing-workflow/SKILL.md)
  - Unit/Integration/E2E failures
  - Mutation testing (Infection)
  - Test coverage < 100%

### Workflow Integration

- **Before committing** → [ci-workflow](../ci-workflow/SKILL.md)

  - Run all checks systematically
  - Fix failures in priority order
  - Ensure all checks pass

- **PR review feedback** → [code-review](../code-review/SKILL.md)
  - Fetch and address PR comments
  - Systematic comment resolution

## Quality Improvement Workflow

### Step 1: Run Comprehensive Checks

```bash
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

```bash
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

- [ci-workflow](../ci-workflow/SKILL.md) - Run comprehensive CI validation
- [complexity-management](../complexity-management/SKILL.md) - Reduce complexity, improve quality
- [deptrac-fixer](../deptrac-fixer/SKILL.md) - Fix architectural violations
- [implementing-ddd-architecture](../implementing-ddd-architecture/SKILL.md) - Understand DDD patterns
- [testing-workflow](../testing-workflow/SKILL.md) - Fix test failures, improve coverage

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

Related Skills

unity-review-quality

16
from diegosouzapw/awesome-omni-skill

Senior Unity Developer quality review. Deep-dives into a Unity project, reviews everything against best practices, and produces a comprehensive HTML report document. Read-only — never modifies any project files. Covers: architecture, code quality, performance, Unity best practices, project health, security, testing, asset management, and technical debt. Use when: (1) Full project quality audit, (2) Pre-release readiness check, (3) Technical debt assessment, (4) Onboarding review to understand project health, (5) Periodic quality gate evaluation, (6) Post-mortem quality analysis. Triggers: 'review quality', 'quality audit', 'project review', 'quality check', 'project health', 'best practices review', 'code audit', 'technical debt review', 'quality report', 'full review', 'project audit'.

testing-quality

16
from diegosouzapw/awesome-omni-skill

Plans and executes comprehensive testing strategy across frontend, backend, and AI tiers. Activates when writing tests, testing features, setting up test infrastructure, checking coverage, running E2E tests, or performance testing. Does not handle writing production code (backend-developer or frontend-developer), vulnerability/security review (security), or infrastructure deployment (devops).

quality

16
from diegosouzapw/awesome-omni-skill

Code quality assurance strategies. Parent skill for quality-related skills: security (security review) and debug (systematic debugging).

analyzing-test-quality

16
from diegosouzapw/awesome-omni-skill

Automatically activated when user asks about test quality, code coverage, test reliability, test maintainability, or wants to analyze their test suite. Provides framework-agnostic test quality analysis and improvement recommendations. Does NOT provide framework-specific patterns - use jest-testing or playwright-testing for those.

applying-a11y-standards

16
from diegosouzapw/awesome-omni-skill

Rules for ensuring Accessibility (a11y) across the Tourly app. Use to build inclusive interfaces.

applying-responsive-standards

16
from diegosouzapw/awesome-omni-skill

Rules for mobile-first responsive design using Tailwind CSS. Use on every UI component to ensure cross-device compatibility.

write-coding-standards-from-file

16
from diegosouzapw/awesome-omni-skill

Write a coding standards document for a project using the coding styles from the file(s) and/or folder(s) passed as arguments in the prompt.

readme-standards

16
from diegosouzapw/awesome-omni-skill

README template structure and required sections

quality-documentation-manager

16
from diegosouzapw/awesome-omni-skill

Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.

documentation-standards

16
from diegosouzapw/awesome-omni-skill

Clear technical documentation with JSDoc, READMEs, Mermaid diagrams, ISMS policy references, and comprehensive code examples

quality-gate

16
from diegosouzapw/awesome-omni-skill

Synthesize all quality assessments (risk, test-design, traceability, NFR) into evidence-based gate decision (PASS/CONCERNS/FAIL/WAIVED) with comprehensive rationale. Generates both YAML (CI/CD) and Markdown (human review) reports with action items. Use during final quality review to make go/no-go deployment decisions based on comprehensive quality evidence.

Naming & Tagging Standards

16
from diegosouzapw/awesome-omni-skill

Establish consistent resource naming conventions and mandatory tagging for cost allocation, security, and governance