Menu
Push current branch to origin, create a GitLab MR if one doesn't exist, and monitor the pipeline until completion
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | push-mr |
| description | Push current branch to origin, create a GitLab MR if one doesn't exist, and monitor the pipeline until completion |
~/.claude/projects/-Users-biedronne-Documents-Work-DS2-synerise-design/memory/gitlab-credentials.mdPRIVATE-TOKEN header)Push the current branch to origin:
git push -u origin HEAD
If the push fails (e.g., rejected), inform the user and stop.
Check if an MR already exists for the current branch:
BRANCH=$(git branch --show-current)
GET https://gitlab.synerise.com/api/v4/projects/1171/merge_requests?source_branch={BRANCH}&state=opened
If an MR already exists, skip to Step 4 (pipeline monitoring). Print the existing MR URL for the user.
If no MR exists, ask the user for a Jira task reference (e.g., STOR-1884). Use the AskUserQuestion tool — suggest a task reference extracted from the branch name if one is present.
Then analyze the changes on the branch to generate a summary of main changes. Use:
git log origin/master..HEAD --oneline
git diff origin/master..HEAD --stat
Create the MR via the GitLab API:
POST https://gitlab.synerise.com/api/v4/projects/1171/merge_requests
Body:
source_branch: current branch nametarget_branch: mastertitle: Use the conventional commit format from the latest commit message (or branch name)description: Use this template, filling in the changes and task reference:Changes:
- <list main changes based on commits and diff>
Resolves task:
- <TASK_REFERENCE>
squash: trueremove_source_branch: truePrint the created MR URL for the user.
After push (whether MR was created or already existed), find the pipeline for the latest commit on the branch:
GET https://gitlab.synerise.com/api/v4/projects/1171/pipelines?ref={BRANCH}&order_by=id&sort=desc&per_page=1
Then poll the pipeline status every 60 seconds:
GET https://gitlab.synerise.com/api/v4/projects/1171/pipelines/{pipeline_id}
Use the Bash tool with run_in_background and a monitoring script that:
success, failed, canceled, or skippedWhile waiting, inform the user that monitoring is in progress and they'll be notified when done.
When the pipeline finishes, fetch the jobs to give a summary:
GET https://gitlab.synerise.com/api/v4/projects/1171/pipelines/{pipeline_id}/jobs
Notify the user with:
Migrate a design-system component off Ant Design to a DS-native styled-components implementation. Encodes the playbook + refinements from the Badge/Typography migrations so each subsequent component is faster. Use when removing antd from a `@synerise/ds-*` package (the antd-removal initiative).
End-to-end DS release — publish bumped packages with lerna, generate a changelog from GitLab MRs, create a Jira release task plus a GitLab release, post a two-audience release changelog to the Teams releases channel, and optionally open DS-upgrade branches/MRs in the portal-ui-bridge and portal-next consumer repos
Add or update an MDX overview documentation page for a component in Storybook, detailing usage patterns, API surface, and implementation guidance.
Audit a design system package for code quality, test coverage, Storybook completeness, and code hygiene issues. Produces a severity-ranked report and a fix plan for critical/important issues.
Verify a component package is ready for publishing by checking documentation, stories, argTypes, code tabs, overview page, unit tests, and interaction tests.
Generate a CLAUDE.md file for a design system component package that documents its structure, API, sub-components, and implementation details for AI-assisted development.