ci-workflow

name	ci-workflow
description	Run comprehensive CI checks before committing changes. Use when the user asks to run CI, run quality checks, validate code quality, or before finishing any task that involves code changes.

CI Workflow Skill

This skill guides you through running comprehensive CI quality checks before committing code changes.

When to Use This Skill

Activate this skill when:

• User explicitly asks to "run CI" or "run quality checks"
• Before finishing any task that involves code changes
• After making significant code modifications
• Before creating a pull request
• When validating code quality

Workflow Steps

1. Run Comprehensive CI Command

Execute the primary CI command that runs all quality checks:

make ci

Expected Outcome: The command MUST output "✅ CI checks successfully passed!" at the end.

2. Monitor CI Execution

The make ci command runs these checks in sequence:

1. Composer validation
2. Security vulnerability analysis
3. Code style fixes (PHP CS Fixer)
4. Static analysis (Psalm)
5. Security taint analysis (Psalm)
6. Code quality analysis (PHPInsights)
7. Architecture validation (Deptrac)
8. Unit tests
9. Integration tests
10. End-to-end tests (Behat)
11. Mutation testing (Infection)

3. Handle Failures

If CI fails (output shows "❌ CI checks failed:"):

1. Identify the failing check from the error output

2. Fix the specific issue:

   • Code style: Review PHP CS Fixer suggestions