drupal-lab

Plugin drupal-lab from marketplace local in cosmicdreams/claude-plugins. Commands read from the repo's manifest — today.

Skills (13)

• analyze-issue

  Analyze one Drupal.org issue by number into a structured report — fetches the issue, filters comments, finds patches and merge requests, assesses complexity. Not for browsing or listing issues (drupal-lab:browse-drupal-issues).

• branch-audit

  Diff what JIRA claims is in a sprint or release against what is actually merged into that branch, producing a delta report a project manager can treat as ground truth. Not for code review or merge-conflict analysis.

• browse-drupal-issues

  Browse or list issues for any Drupal.org project (core or contrib) via RSS. Not for deep analysis of a single issue — use drupal-lab:analyze-issue.

• config

  Discover and configure drupal-lab integrations into ~/.claude/drupal-lab.json — probes DDEV and Acquia CLI, finds Drupal project roots, asks about naming conventions and Drupal.org credentials. Run on first setup or when a drupal-lab skill cannot find its project.

• ddev

  Run Drupal tooling inside DDEV containers: phpcs, phpstan, phpunit, drush, composer. Host-side PHP will fail — DDEV supplies PHP, the database, Chrome webdriver, and test environment variables. Not for DDEV lifecycle (drupal-lab:process-lifecycle).

• finish-issue

  Close out a Drupal issue worktree with a deliberate decision — submit as merge request, submit as patch, park as work-in-progress, or discard — then shut down DDEV and clean up. The final step, not for mid-implementation.

• issue-summary

  Write a short Drupal.org contribution comment (what was fixed, the proof, what was not checked) once the fix passes the worth-it gate, from the analysis report and the git diff. Run only after drupal-lab:validate-patch passes.

• module-dev-starter

  Scaffold a Claude-ready Drupal contrib module project with DDEV — runs admin:scaffold, then adds Drupal directories, DDEV config, and composer setup. Not for Drupal core work (drupal-lab:process-lifecycle).

• perf-measure

  Profile PHP inside DDEV — page load, memory allocation, database query patterns — emitting JSON score tuples for the experiment ratchet, including callgraph_top_10. Not for frontend performance (test-lab:perf-measure).

• process-lifecycle

  Manage the DDEV lifecycle for a Drupal worktree: start, ready-check, completion, shutdown, cleanup. Not for running tools inside DDEV — use drupal-lab:ddev.

• release-cut

  Cut a release assembly branch from main and merge the feature branches a JIRA release ticket approves. Release branches are disposable and rebuilt from scratch each run. Not for feature or sprint branches (drupal-lab:sprint-start).

• sprint-start

  Create a sprint assembly branch named for the active JIRA sprint and seed its manifest of expected tickets. Rebuilt from main each run, never edited in place. Not for feature branches or release branches (drupal-lab:release-cut).

• validate-patch

  Run every quality gate against a Drupal patch or merge request before submission — phpcs, phpstan, phpunit, and coverage review via DDEV. Not for issue research (drupal-lab:analyze-issue).

Subagents (1)

• reviewer

  Fresh-context review of a Drupal issue fix before it is submitted. Checks the diff against the issue and its spec first, then runs the quality gates and looks for untested changes. Writes results.json. Use after drupal-lab:validate-patch passes and before drupal-lab:issue-summary.

Hooks (1)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/branch-guard.sh

Similar plugins