Open
Conversation
cableman
requested changes
Feb 26, 2026
| "check itk-dev standards", (3) reviewing PR for convention compliance, | ||
| (4) setting up a new itk-dev project, (5) upgrading Docker configuration. | ||
| Walks through 9 validation areas: MCP tool comparison, docker-compose, | ||
| server compose, environment, Taskfile, Symfony/PHP config, Composer, |
Contributor
There was a problem hiding this comment.
Symfony/PHP config this would limit the usage to symfony projects or?
|
|
||
| Before manual checks, attempt automated comparison using the | ||
| `plugin:itkdev-tools:itkdev-docker` MCP tools. These provide | ||
| file-level diffs against the canonical template. |
Contributor
There was a problem hiding this comment.
The big question is how do we handle extra service etc. or would exceptions to the rules be handled in the projects memory files
| - [ ] `phpfpm` uses `itkdev/php8.4-fpm:latest` (or appropriate PHP version) | ||
| - [ ] `mariadb` uses `itkdev/mariadb:latest` | ||
| - [ ] `nginx` uses `nginxinc/nginx-unprivileged:alpine` | ||
| - [ ] `worker` uses `itkdev/supervisor-php8.4:alpine` (matching PHP version) |
Contributor
There was a problem hiding this comment.
Worker it only in this or some projects. Many default projects would use a docker-compose.override.yml file to add/unset services form the default setup.
|
|
||
| #### Dev Profile Services | ||
|
|
||
| - [ ] `node`, `markdownlint`, `prettier` services have `profiles: [dev]` |
Contributor
There was a problem hiding this comment.
Normally they would be added in docker-compose.override.yml
|
|
||
| ### Step 3 — Environment (`.env`) | ||
|
|
||
| Validate environment file conventions. |
Contributor
There was a problem hiding this comment.
This is mainly for symfony projects only
|
|
||
| --- | ||
|
|
||
| ### Step 4 — Taskfile.yml |
Contributor
There was a problem hiding this comment.
Not sure we have a taskfile standard... may simple task required only. Link task compose, task drush, task console... based on project type
yepzdk
added a commit
that referenced
this pull request
Feb 27, 2026
Address PR #29 review feedback: remove Symfony-centric assumptions and make the skill flexible for Symfony, Drupal, and generic project types. - Add project type classification (symfony-*/drupal-*/generic) after Step 0 - Support documented project exceptions via CLAUDE.md - Make worker service and dev profile services conditional in Step 1 - Restructure Taskfile checks into required/conditional/optional tiers - Rename Step 5 to "Framework-Specific Config" with per-type checks - Split GitHub Actions workflow list by project type - Update verification report template with documented exceptions
Add skill for auditing projects against itk-dev Docker and development conventions from itk-dev/devops_itkdev-docker. Includes automated MCP tool comparison and 9-area manual validation checklist.
Align with the itkdev- prefix convention used by all other skills.
Address PR #29 review feedback: remove Symfony-centric assumptions and make the skill flexible for Symfony, Drupal, and generic project types. - Add project type classification (symfony-*/drupal-*/generic) after Step 0 - Support documented project exceptions via CLAUDE.md - Make worker service and dev profile services conditional in Step 1 - Restructure Taskfile checks into required/conditional/optional tiers - Rename Step 5 to "Framework-Specific Config" with per-type checks - Split GitHub Actions workflow list by project type - Update verification report template with documented exceptions
yepzdk
force-pushed
the
feature/itkdev-validate-standards
branch
from
c96eb4b to
63c3fe6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
itkdev-validate-standardsskill for auditing projects against itk-dev Docker and development conventions fromitk-dev/devops_itkdev-dockeritkdev-dockerMCP tools (detect, compare, fetch template content)Test plan