القائمة
Use when a product manager asks for a MetalMart playground feature or code change and wants the full implementation workflow run through branch, PR, preview build, and preview handoff.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when a developer asks for a MetalMart shop change that must be implemented and verified end-to-end with local mirrord and Playwright before handoff.
Use when running one MetalMart shop service locally under mirrord against the playground GKE cluster. Requires Playwright UI verification for catalog or frontend-affecting changes, not curl alone.
Use when a developer asks for a MetalMart shop change that must be implemented and verified end-to-end in a mirrord preview environment with Playwright before handoff.
Use when a PM or developer wants a MetalMart shop change implemented, pushed to a PR, and exposed through the mirrord preview workflow for human review after the preview build succeeds.
Use when the user explicitly wants the current local git changes reviewed, committed on a new branch, pushed to origin, and opened as a pull request.
Use when the user wants the playground repo built and deployed to local minikube for testing, including changed service images, `overlays/local`, readiness checks, and local access URLs.
| name | pm-feature-workflow |
| description | Use when a product manager asks for a MetalMart playground feature or code change and wants the full implementation workflow run through branch, PR, preview build, and preview handoff. |
This skill automates the end-to-end workflow for PM-driven MetalMart changes in this repo.
Read docs/AI_ROOT_CONTEXT.md first.
The full branch is used for checkout and Docker tag input. The preview key and
baggagerouting value are the branch's final path segment after/.
main.The preview key is the full branch if there is no slash, or the part after the final slash. The
preview key must match ^[a-z]+-[a-z]+$.
feature/ are allowed because they are not part of the preview keyExamples:
product-searchfeature/product-searchcart-fixaviram/cart-fixcheckout-buttonIf the preview key does not match the rule, delete the branch and recreate it correctly before continuing.
Typical paths:
apps/shop/metal-mart-frontend/apps/shop/<service-name>/Use a standard commit message such as:
feat(frontend): add product search functionalityfix(order-service): correct total calculationstyle(checkout): update button colorsPreferred:
gh pr create --title "<title>" --body "<body>" --base main --head <branch>
Fallback:
gh is unavailable.After the PR is opened, do not present the preview until the preview build succeeds.
preview-shop-pr.yml run for the branch or PR.Between polls, give the PM one short status update. Reuse a rotating set of messages such as:
mirrord is spinning up your preview environment...Building your preview pod image...Deploying your changes into the preview environment...mirrord is wiring up traffic splitting for your branch...Preview environment is warming up...If the workflow fails:
When the preview succeeds, return:
https://playground.metalbear.dev/shopbaggage: mirrord-session=<preview-key>https://preview.metalbear.dev/<preview-key>/shopAlso provide concise testing instructions using either the mirrord browser extension, curl, or a request-header tool.