Agent skill
ci-workflow
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/ci-workflow-vilnacrm-org-user-service-2
SKILL.md
CI Workflow Skill
Context (Input)
- Code changes exist in the working directory
- Ready to validate code quality before commit/PR
- Need to ensure all quality standards are met
Task (Function)
Execute make ci and ensure ALL quality checks pass with success message.
Success Criteria: Output ends with "✅ CI checks successfully passed!"
Parallel Execution
The CI command uses Make's built-in parallelism (make -j4 --output-sync=target) for concurrent execution. No external tools are required beyond GNU Make.
Checks run in two stages:
- Preflight (sequential):
phpcsfixer → phpmd → phpinsights - Parallel stage: static analysis, deptrac, tests+openapi, mutation
Parallel stage groups:
| Group | Tasks | Dependency |
|---|---|---|
| Static Analysis | composer-validate, check-requirements, check-security, psalm, psalm-security | None (fully parallel) |
| Architecture | deptrac | None |
| Tests + OpenAPI | unit-tests, integration-tests, behat, openapi-diff, spectral, schemathesis | setup-test-db first |
| Mutation | infection | None |
AI-Friendly Output
Make's --output-sync=target flag groups each target's output together after completion, preventing interleaved output from parallel tasks.
Execution Steps
Step 1: Run CI
make ci
Step 2: Check Result
- ✅ Success: "✅ CI checks successfully passed!" → Task complete
- ❌ Failure: Task fails with error output → Go to Step 3
Step 3: Fix Failures
Identify failing check from output and apply fix:
| Check | Command | Fix |
|---|---|---|
| Code style | make phpcsfixer |
Apply auto-fixes |
| Static analysis | make psalm |
Fix type errors |
| Quality metrics | make phpinsights |
Reduce complexity, fix architecture |
| Tests | make unit-tests |
Debug failing tests |
| Mutations | make infection |
Add missing test cases |
Step 4: Re-run
make ci
Repeat Steps 2-4 until success message appears.
Alternative Commands
| Command | Description |
|---|---|
make ci |
Run parallel CI (default, faster) |
make ci-sequential |
Run sequential CI (fallback) |
make ci-preflight |
Run mutating preflight checks only |
Constraints (Parameters)
NEVER decrease these thresholds:
- min-quality: 100%
- min-complexity: 93%
- min-architecture: 100%
- min-style: 100%
- mutation MSI: 100%
- test coverage: 100%
DO NOT:
- Lower quality thresholds
- Skip failing checks
- Commit without "✅ CI checks successfully passed!" message
- Run commands outside Docker container (use
makeordocker compose exec php)
Format (Output)
Required final output:
✅ CI checks successfully passed!
Verification Checklist
-
make ciexecuted - All checks passed (composer, security, style, psalm, tests, mutations)
- Output shows "✅ CI checks successfully passed!"
- Zero test failures
- Zero escaped mutants
- No quality threshold decreased
Rollback
If parallel execution causes issues:
- Use
make ci-sequentialfor the original sequential behavior
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
majiayu000/claude-skill-registry
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
majiayu000/claude-skill-registry
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?