Menu
Generate and validate .gitlab-ci.yml files for Drupal modules using Drupal Association templates. Use this skill when you need to create GitLab CI configuration, update existing CI, or validate CI setup for a Drupal module.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | drupaltools-contrib-gitlab-ci |
| description | Generate and validate .gitlab-ci.yml files for Drupal modules using Drupal Association templates. Use this skill when you need to create GitLab CI configuration, update existing CI, or validate CI setup for a Drupal module. |
Generate .gitlab-ci.yml configuration for Drupal modules using the official Drupal Association template.
Use this skill when:
Read MODULE.info.yml to determine core_version_requirement:
grep "core_version_requirement" MODULE.info.yml
| Drupal Version | PHP Versions |
|---|---|
| ^10 | 8.1, 8.2, 8.3 |
| ^11 | 8.2, 8.3, 8.4 |
Fetch the official Drupal Association template:
curl -sS "https://git.drupalcode.org/project/gitlab_templates/-/raw/1.0.x/gitlab-templates/.gitlab-ci.yml"
The generated .gitlab-ci.yml includes:
| Job | Purpose |
|---|---|
composer_validate | Validate composer.json |
php_syntax | PHP syntax checking |
phpcs | Drupal coding standards (PHPCS) |
phpstan | Static analysis (PHPStan) |
phpunit | Unit tests (if tests/ exists) |
image: git.drupal.orgqa/travis-ci:latest
stages:
- Static analysis
- Testing
variables:
SIMPLETEST: "https://git.drupalcode.org/project/drupal.git"
# ...
phpcs:
stage: Static analysis
script:
- composer install --no-interaction
- composer validate --strict
- ./vendor/bin/phpcs --standard=Drupal,DrupalPractice --extensions=php,module,inc,install,test,profile,theme,css,info,txt,md,yml
phpstan:
stage: Static analysis
script:
- composer install --no-interaction
- ./vendor/bin/phpstan analyse --no-progress
phpunit:
stage: Testing
script:
- composer install --no-interaction
- ./vendor/bin/phpunit --configuration=phpunit.xml
If your module has tests:
ls tests/ 2>/dev/null && echo "has_tests"
phpunit:
stage: Testing
matrix:
- PHP_VERSION: "8.1"
- PHP_VERSION: "8.2"
- PHP_VERSION: "8.3"
phpcs:
stage: Static analysis
matrix:
- Drupal: "10.3"
- Drupal: "11.0"
Check if .gitlab-ci.yml is properly configured:
yamllint| Issue | Solution |
|---|---|
| Template outdated | Regenerate from latest template |
| PHP version mismatch | Update based on core_version_requirement |
| Missing composer.lock | Run composer update and commit |
| Tests fail | Fix locally with vendor/bin/phpunit |
Run the project markdownlint script in a Drupal project and fix the reported markdown violations. Use this skill whenever the user asks to run markdownlint, lint markdown, check the docs, or says "run scripts/markdownlint.sh and fix the errors".
Run PHPCS in a Drupal project and fix the reported coding standards violations. Use this skill whenever the user asks to run phpcs, check coding standards, fix code style errors, lint PHP/Drupal code, or says things like "run phpcs and fix the errors" or "clean up my coding standards".
Run PHPStan static analysis in a Drupal project and resolve the reported errors. Use this skill whenever the user asks to run phpstan, run static analysis, fix type errors, or says "run phpstan and fix the errors".
Run the custom PHPUnit test suite in a Drupal project and fix the reported failures and errors. Use this skill whenever the user asks to run phpunit, run the tests, run the custom testsuite, or says "run phpunit and fix the errors".
Estimate costs and timeline for Drupal projects using a structured breakdown of tasks, roles, content types, and development work. Use this skill when the user asks for a project quote, cost breakdown, timeline estimation, budget planning, or resource allocation for a Drupal website. Trigger for requests like "how much would this Drupal project cost", "estimate this project", "create a quote", "plan the budget", or any discussion about pricing/timeline for Drupal development.
Create a Drupal.org issue title and summary body that is ready to paste into the issue form. Use when the user asks to draft, improve, or rewrite an issue from a bug report, feature request, patch, MR, commit, or discussion. When the user says "issue title", "issue body", "issue summary", or similar.