원클릭으로
drupal-sdlc-plugin
drupal-sdlc-plugin에는 axelerant에서 수집한 skills 11개가 있으며, 저장소 수준 직업 범위와 사이트 내 skill 상세 페이지를 제공합니다.
이 저장소의 skills
Fix PHPStan, PHPCS, twigcs, and yamllint violations from error output. Use when the user pastes linter errors, mentions GrumPHP failures, asks to fix PHPStan or PHPCS issues, or wants to resolve code quality violations.
Generate Drupal config YAML files from plain English descriptions. Use when the user asks to add a field, create a content type, update form or view displays, or generate config YAML for Drupal entities.
Urgent fix bypass workflow: read ticket, branch, fix, validate, PR. Skips spec-writer for speed. Use when told to hotfix a Jira ticket or for urgent bug fixes.
Generate complete Drupal custom module boilerplate, especially for API integrations. Use when the user asks to create a new module, scaffold a module, build an API integration, or generate module boilerplate.
Run post-install setup for the drupal-sdlc plugin. Auto-detects project values, verifies gh CLI and MCP connectivity. Use after installing the plugin on a new project, or when MCPs show as failed.
Create a pull request from completed work. Generates PR title, description, what changed, test plan, and risk level. Always run the validate skill before using this.
Review a PR diff and flag risks, run security checklist, verify AC coverage, and score risk level. Use this before merging any PR.
Turn a plain English feature idea into a structured Drupal spec with numbered acceptance criteria, test mapping, and specific Drupal constructs. Always use this first before building anything new.
Generate Playwright specs and PHPUnit tests for Drupal projects. Use when the user asks to write tests, generate test specs, improve test coverage, create Playwright tests, or write unit tests for services.
Run full validation on recent changes including linting, config import, config round-trip check, Playwright screenshots, and tests. Use after completing a feature, when asked to validate work, or when verifying that changes are correct.
Pick up a Jira ticket and run the complete SDLC loop autonomously. Use when told to work on a Jira ticket key like TDP-4 or PROJ-12.