菜单
Creates a PrestaShop pull request with the required metadata table. Triggers when asked to create, open, submit, or push a PR, or when mentioning "pull request" in the context of contributing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Complete PrestaShop module development workflow using modern architecture and best practices. Use when: creating new PrestaShop modules, updating legacy modules to modern code, implementing hooks and actions, setting up module configuration pages, adding front office features, handling database operations, implementing security measures, managing translations, creating cart rules and vouchers, building Symfony console commands, or modernizing existing PrestaShop modules from legacy patterns to current standards.
Create the form page actions in the admin controller: create (add) and edit, plus any entity-specific actions. Uses FormBuilder/FormHandler pattern — never builds commands directly. Trigger: "create form actions for {Domain}", "create add/edit for {Domain}".
Create the repository in the Adapter layer. This is the ONLY class that touches the database — all handlers delegate to it. Covers multistore patterns with ShopConstraint when the entity requires it. Trigger: "create repository for {Domain}".
Create the form data flow layer: DataProvider (loads entity data for edit form), DataHandler (dispatches commands on create/update), error handling, and service registration. This bridges the form layer with the CQRS layer. Read Component/Forms/CONTEXT.md for conventions. Trigger: "create form data handling for {Domain}".
Create a multi-tab form layout using PrestaShop's NavigationTabType. This is a specific pattern for complex forms with many fields organized by tabs — NOT the default form layout. Most forms do not need tabs. Trigger: "create tab layout for {Domain} form", "add tabs to {Domain} form".
Create the Symfony form type for an entity's add/edit form. Covers standard field types, translatable fields, money fields, file uploads, and choice providers. For multi-tab layout with NavigationTabType, see create-form-tab-layout. Trigger: "create form type for {Domain}".
| name | create-pr |
| description | Creates a PrestaShop pull request with the required metadata table. Triggers when asked to create, open, submit, or push a PR, or when mentioning "pull request" in the context of contributing. |
| allowed-tools | Read, Grep, Glob, Bash, Agent |
Guide a contributor through creating a pull request that complies with the PrestaShop contribution guidelines, including the mandatory metadata table.
.github/PULL_REQUEST_TEMPLATE.md — this is the single source of truth for the table format.git log and git diff against the target branch to understand what changed..ai/CONTEXT.md).From code analysis and git context, infer as much as possible:
| Field | How to infer |
|---|---|
| Branch | Current git branch or merge target |
| Description | Summarize from commits and diff. Be specific (versions, browser/server config, module/theme). |
| Type | bug fix · improvement · new feature · refacto — infer from changes |
| Category | FO · BO · CO · IN · WS · TE · LO · ME · PM — infer from files changed. See category reference. |
| BC breaks | Analyze public API changes → yes / no |
| Deprecations | Check for new @deprecated annotations → yes / no |
| How to test | Write step-by-step verification instructions from the PR context |
| Fixed issue | Extract from conversation, branch name (e.g. fix/12345), or commit messages. Format: Fixes #<number> |
For any required field (Branch, Description, Type, Category, BC breaks, Deprecations) that cannot be confidently determined, ask the user. Do not guess.
Optional fields (UI Tests, Related PRs, Sponsor company) — fill when known, leave the template placeholder otherwise.
Use GitHub MCP tools (mcp__github__create_pull_request) or gh pr create CLI to create the PR with the filled-in template as the body.
The created PR URL, displayed to the user.