القائمة
Commit, push, and open a GitLab Merge Request following this repo's promotion chain (dev -> stage -> prod). Use on "create pr", "create mr", "open a pr/mr", "/create-pr", or "promote <branch>".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | create-pr |
| description | Commit, push, and open a GitLab Merge Request following this repo's promotion chain (dev -> stage -> prod). Use on "create pr", "create mr", "open a pr/mr", "/create-pr", or "promote <branch>". |
This repo is on GitLab (<your-gitlab-project>). "PR" = Merge Request. Use the glab CLI
(already installed). Environment branches are promoted along a fixed chain - never open an MR
straight to prod from a feature/dev branch.
| Source (current) branch | MR target | Notes |
|---|---|---|
dev (default working) | stage | Promote accumulated work to the staging env |
stage | prod | Promote staging -> production |
any feat/* / fix/* / <KEY>-* | dev | Feature/ticket work merges into dev first |
If the current branch isn't in the table, target dev.
git branch --show-current -> look it up in the
table above to get the target.git status -s. Commit ONLY changes that belong to this
unit of work. If unrelated/pre-existing edits are present, do NOT bundle them -
stage your files explicitly and tell the user what you left out. Never
git add -A blindly when foreign changes are in the tree.feat:, fix:, docs:, refactor:,
chore:); for ticket work prefix the ticket key (e.g. feat(<KEY>-123): ...).pnpm check:types && pnpm check:lint). Don't push a red tree.dev, stage, prod)
without that explicit yes is forbidden. Only after the yes: git push -u origin <current>.glab mr create --source-branch <current> --target-branch <target> \
--title "<type>: <summary>" --description "<body>" --yes --remove-source-branch=false
dev, stage, prod) NEVER pass
--remove-source-branch. Reuse an existing open MR for the same source->target
instead of creating a duplicate
(glab mr list --source-branch <current> --target-branch <target>).Deliver an OSS platform-core feature end-to-end: context collection -> plan + approval -> implementation -> unit/integration tests -> e2e test cases + run -> fixes -> create-pr -> Jira transition (only on explicit ask) -> Slack notice. Fed by a work-order (from the consumer add-feature handoff) or an OSS ticket. Use on "add feature", "plan <work-order>", "deliver this OSS change", or /add-feature [path|ticket]. Read-only until the plan is approved; never pushes without explicit OK.
Multi-agent code review of the working branch against this repo's conventions, boundaries, contracts, security, messaging, and audit rules. Fans out a configurable number of parallel reviewers, each grounded in the rule docs, then synthesizes one verdict. Use on "review this", "oss review", "/oss-review", optionally "--agents N", "--base <ref>", "--fix", a GitHub PR number, or paths.
Context-aware PR review - gathers ticket AC + PR discussion, reviews from fixed angles (security, performance, duplication, simplification, conventions, igaming fit), and returns line-anchored draft comments plus a one-sentence go/no-go. Token-budgeted so it runs fine on capped plans. Use on "review", "/review", "review this PR", optionally a PR number or "--base <ref>".
Deliver a feature end-to-end in this consumer repo. Aggregates context (Jira + Confluence + Slack + Google Drive + Notion + local docs + past sessions + codebase), produces an approved plan, then drives delivery by calling sibling skills - create-plugin (build), review, create-pr (MR) - and create-task for ticket hygiene. Transitions Jira (no comments) and drafts a one-line Slack notice. Use on "add feature", "plan <KEY>-XXX", "deliver <KEY>-XXX", or /add-feature [<KEY>-XXX]. Read-only until the plan is approved; never pushes, transitions Jira, or sends Slack without OK.
Guided creation of an extension - the right way to add behavior or swap a vendor without touching `@openora/*` core. Interviews for intent, classifies the seam (plugin / adapter / page / route), runs the matching scaffold command, wires extensions.config.ts, and enforces boundaries + audit + db rules. Use on "create plugin", "add an extension", "swap KYC/PSP", "mount a page", "/create-plugin <name>".
Create a frontend feature module in apps/backoffice or apps/web following ADR-0001's modular architecture: standard folder shape, co-located locales, DI hooks, pure components, barrel entry, route wiring. Use on "create module", "new feature module", "add a backoffice/web module", "/create-ui-module <app> <name>".