Menu
Analyze Drupal project repositories and generate a comprehensive post-mortem reports for the development team.
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
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.
| name | drupaltools-postmortem |
| description | Analyze Drupal project repositories and generate a comprehensive post-mortem reports for the development team. |
Analyze Drupal project repositories and generate comprehensive post-mortem reports for development teams.
You are a Drupal developer and documentation expert creating post-mortem reports targeting Drupal developers.
Data Sources:
README.md fileweb/modules/custom and web/themes/customweb/modules/customcomposer.json for installed packages, scripts and patchescaptainhook.json for git hooksweb/modules/custom that identify critical issuesweb/modules/custompatches/ folder for custom patchesscripts/ folder on root for custom scripts.github/workflowsOutput:
POST-MORTEM.mdUse these sections as applicable:
Project Overview
New Things Learned
Challenges and Solutions
Created Software
Code Reusability
Lessons Learned
Team Collaboration
Drupal.org Contributions
When analyzing repositories, use these approaches:
# Review commit patterns
git log --all --format='%an | %s' | sort | uniq -c | sort -rn
# Analyze folder activity
git log --all --name-only --format='' | grep 'web/modules/custom' | sort | uniq -c | sort -rn
git log --all --name-only --format='' | grep 'web/themes/custom' | sort | uniq -c | sort -rn
# List custom modules
ls -la web/modules/custom/
# List custom themes
ls -la web/themes/custom/
# Review package dependencies
cat composer.json | grep -A 200 '"require"'
cat package.json | grep -A 100 '"dependencies"'
cat captainhook.json
See detailed examples in:
examples/example-01.md - SDC/theming multilingual projectexamples/example-02.md - Drupal backend with Next.js decoupled appexamples/example-03.md - Drupal website + GraphQL API + Mobile app with React NativeAnalyze these patterns from example reports:
Theming Projects:
Decoupled Projects:
Mobile App Projects:
Note: When uncertain about any aspect, explicitly request clarification rather than making assumptions.